Method of transmitting omnidirectional video, method of receiving omnidirectional video, device for transmitting omnidirectional video, and device for receiving omnidirectional video

ABSTRACT

According to an aspect of the present invention, a method for transmitting omnidirectional video is disclosed. The method of transmitting omnidirectional video according to an embodiment of the present invention includes acquiring an image for the omnidirectional video, projecting the image for the omnidirectional video onto a 3D projection structure, packing the image projected onto the 3D projection structure in a 2D frame, encoding the image packed into the 2D frame, and transmitting a data signal containing the encoded image and metadata about the omnidirectional video.

This application claims the benefit of U.S. Provisional Patent Application No. 62/379,740, filed on Aug. 25, 2016, and U.S. Provisional Patent Application No. 62/444,814, filed on Jan. 11, 2017, which are hereby incorporated by reference as if fully set forth herein.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to methods and devices for transmitting and receiving omnidirectional media, and more particularly, to methods and devices for transmitting and receiving omnidirectional video and metadata related to the omnidirectional video.

Discussion of the Related Art

As analog broadcast signal transmission is terminated, various technologies for transmitting and receiving a digital broadcast signal have been developed. A digital broadcast signal is capable of containing a larger amount of video/audio data than an analog broadcast signal and further containing various types of additional data as well as video/audio data.

A virtual reality (VR) system provides, to a user, the experience of being in an electronically projected environment. The VR system can be enhanced in order to provide images with higher definition and spatial sounds. The VR system can allow a user to interactively use VR content.

SUMMARY OF THE INVENTION

The VR system needs to be enhanced in order to more efficiently provide VR environments to users. To this end, it is necessary to provide data transmission efficiency for transmission of a large amount of data such as VR content, robustness between transmission and reception networks, network flexibility considering a mobile receiver, efficient reproduction and a signaling method, etc.

The present invention proposes methods for effectively providing omnidirectional video services by defining and delivering metadata about attributes of omnidirectional video when omnidirectional video content is provided.

The specification discloses methods of defining, storing and signaling metadata related to omnidirectional video such that a user can view a view (point) or a region intended by a producer in reproduction of the omnidirectional video. Specific methods are as follows.

A method of defining, storing and signaling metadata about region information in a 2D space is disclosed.

A method of defining, storing and signaling metadata about viewpoint (point) information in a 2D space is disclosed.

A method of defining, storing and signaling metadata about region information in a 3D space is disclosed.

A method of defining, storing and signaling metadata about viewpoint (point) information in a 3D space is disclosed.

A method of signaling a relationship between a metadata track regarding region information or viewpoint (point) information and an omnidirectional video track is disclosed.

A method of transmitting and signaling metadata using DASH is disclosed.

A method of transmitting and signaling metadata using MPEG-2 TS is disclosed.

A method of transmitting and signaling metadata using a video coding layer (VCL) is disclosed.

The specification discloses methods of defining, storing and signaling metadata about GPS information related to video in reproduction of omnidirectional video. Specific methods are as follows.

A method of defining, storing and signaling metadata about GPS related information is disclosed.

A method of signaling a relationship between a metadata track regarding GPS related information and an omnidirectional video track.

The specification also discloses a process of transmitting and receiving omnidirectional media content and associated metadata about an omnidirectional video service.

The specification also discloses a method of transmitting and receiving ROI (Region Of Interest) metadata about a point-in-time (point) or region intended by a producer, or statistically preferred viewport (point) or region.

The present invention can efficiently transmit omnidirectional content in an environment supporting future hybrid broadcast using terrestrial broadcast networks and the Internet.

The present invention can propose methods for providing interactive experience in omnidirectional content consumption of users.

The present invention can propose signaling methods for correctly reflecting intention of omnidirectional content producers in omnidirectional content consumption of users.

The present invention can propose methods of efficiently increasing transmission capacity and delivering necessary information in omnidirectional content delivery.

The present invention can propose methods for effectively providing omnidirectional video services by defining and delivering metadata about attributes of 360-degree video when omnidirectional video content is provided.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an architecture for providing 360-degree video according to the present invention.

FIG. 2 illustrates a 360-degree video transmission device according to one aspect of the present invention.

FIG. 3 illustrates a 360-degree video reception device according to another aspect of the present invention.

FIG. 4 illustrates a 360-degree video transmission device/360-degree video reception device according to another embodiment of the present invention.

FIG. 5 illustrates the concept of aircraft principal axes for describing a 3D space according to the present invention.

FIG. 6 illustrates projection schemes according to one embodiment of the present invention.

FIG. 7 illustrates tiles according to one embodiment of the present invention.

FIG. 8 illustrates 360-degree video related metadata according to one embodiment of the present invention.

FIG. 9 illustrates a media file structure according to one embodiment of the present invention.

FIG. 10 illustrates a hierarchical structure of boxes in ISOBMFF according to one embodiment of the present invention.

FIG. 11 illustrates overall operation of a DASH based adaptive streaming model according to one embodiment of the present invention.

FIG. 12 illustrates metadata about region information in a 2D space according to one embodiment of the present invention.

FIG. 13 illustrates metadata about viewpoint (point) information in a 2D space according to one embodiment of the present invention.

FIG. 14 illustrates metadata about region information in a 3D space according to one embodiment of the present invention.

FIG. 15 illustrates metadata about an individual region to be represented in a 3D space according to various embodiments of the present invention.

FIG. 16 illustrates metadata about region information in a 3D space according to another embodiment of the present invention.

FIG. 17 illustrates metadata about region information in a 3D space according to another embodiment of the present invention.

FIG. 18 illustrates metadata about region information in a 3D space according to another embodiment of the present invention.

FIG. 19 is a reference diagram illustrating a method of defining a region by a region type according to an embodiment of the present invention.

FIG. 20 illustrates a tref box according to one embodiment of the present invention.

FIG. 21 illustrates metadata about a GPS according to one embodiment of the present invention.

FIG. 22 illustrates an MPD signaling transmission of metadata about region information or viewpoint information according to one embodiment of the present invention.

FIG. 23 illustrates an MPD signaling transmission of metadata about region information or viewpoint information according to another embodiment of the present invention.

FIG. 24 is a block diagram of a receiver according to one embodiment of the present invention.

FIG. 25 illustrates an MPD signaling transmission of metadata about region information or viewpoint information according to another embodiment of the present invention.

FIG. 26 is a block diagram of a receiver according to another embodiment of the present invention.

FIG. 27 illustrates an MPD signaling transmission of metadata about region information or viewpoint information according to another embodiment of the present invention.

FIG. 28 illustrates an MPD signaling transmission of metadata about region information or viewpoint information according to another embodiment of the present invention.

FIG. 29 is a block diagram of a receiver according to another embodiment of the present invention.

FIG. 30 illustrates a stream identifier and information on a stream allocated to the stream identifier.

FIG. 31 illustrates a stream type and part of information on a stream allocated to the stream type.

FIG. 32 illustrates an access unit transmitted through a PES packet.

FIG. 33 illustrates an adaptation field according to one embodiment of the present invention.

FIG. 34 illustrates an extension descriptor according to one embodiment of the present invention.

FIG. 35 illustrates values of an extension descriptor tag included in the extension descriptor and description of the values.

FIG. 36 illustrates a vdci extension descriptor according to one embodiment of the present invention.

FIG. 37 illustrates a 2D vdci descriptor according to one embodiment of the present invention.

FIG. 38 illustrates a spherical vcdi descriptor according to one embodiment of the present invention.

FIG. 39 is a block diagram of a receiver according to another embodiment of the present invention.

FIG. 40 illustrates metadata about region information or viewpoint information, which is included in an SEI message, according to one embodiment of the present invention.

FIG. 41 illustrates metadata about region information or viewpoint information, which is included in an SEI message, according to another embodiment of the present invention.

FIG. 42 is a block diagram of a receiver according to another embodiment of the present invention.

FIG. 43 is a diagram illustrating a process of transmitting and receiving content and metadata about a 360-degree video service according to an embodiment of the present invention.

FIG. 44 illustrates an example of information included in rendering metadata and projection/mapping metadata according to an embodiment of the present invention.

FIG. 45 illustrates a box including projection/mapping metadata according to another embodiment of the present invention.

FIG. 46 is a diagram illustrating a process of transmitting and receiving content and metadata about a 360-degree video service according to another embodiment of the present invention.

FIG. 47 is a diagram illustrating a process of transmitting and receiving content and metadata about a 360-degree video service according to another embodiment of the present invention.

FIG. 48 illustrates ROI metadata according to an embodiment of the present invention.

FIG. 49 is a flowchart illustrating a method of transmitting omnidirectional video according to one embodiment of the present invention.

FIG. 50 is a block diagram of a device for transmitting omnidirectional video according to one embodiment of the present invention.

FIG. 51 is a flowchart illustrating a method of receiving omnidirectional video according to one embodiment of the present invention.

FIG. 52 is a block diagram of a device for receiving omnidirectional video according to one embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. The detailed description, which will be given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present invention, rather than to show the only embodiments that can be implemented according to the present invention.

Although most terms of elements in this specification have been selected from general ones widely used in the art taking into consideration functions thereof in this specification, the terms may be changed depending on the intention or convention of those skilled in the art or the introduction of new technology. Some terms have been arbitrarily selected by the applicant and their meanings are explained in the following description as needed. Thus, the terms used in this specification should be construed based on the overall content of this specification together with the actual meanings of the terms rather than their simple names or meanings.

FIG. 1 illustrates an architecture for providing 360-degree video according to the present invention.

The present invention proposes a method for providing 360-degree content or omnidirectional media in order to provide VR (Virtual Reality) to users. VR refers to a technique or an environment for replicating an actual or virtual environment. VR artificially provides sensuous experiences to users and thus users can experience electronically projected environments.

360-degree content refers to convent for realizing and providing VR and may include 360-degree video and/or 360-degree audio. 360-degree video may refer to video or image content which is necessary to provide VR and is captured or reproduced in all directions (360 degrees). 360-degree video may refer to video or an image represented on 3D spaces in various forms according to 3D models. For example, 360 video can be represented on a spherical plane. 360 audio is audio content for providing VR and may refer to spatial audio content which can be recognized as content having an audio generation source located on a specific space. 360 content may be generated, processed and transmitted to users, and users may consume VR experiences using the 360 content. Hereinafter, 360 content/video/image/audio may be represented as 360 content/video/image/audio without a unit (degree) or VR content/video/image/audio. Further, 360 content/video/image/audio may be used interchangeably with omnidirectional content/video/image/audio.

The present invention proposes a method for effectively providing 360 degree video. To provide 360 video, first, 360 video may be captured using one or more cameras. The captured 360 video is transmitted through a series of processes, and a reception side may process received data into the original 360 video and render the 360 video. Accordingly, the 360 video can be provided to a user.

Specifically, a procedure for providing 360 video may include a capture process, a preparation process, a transmission process, a processing process, a rendering process and/or a feedback process.

The capture process may refer to a process of capturing images or videos for a plurality of viewpoints through one or more cameras. An image/video data t1010 shown in the figure can be generated through the capture process. Each plane of the shown image/video data t1010 may refer to an image/video for each viewpoint. The captured images/videos may be called raw data. In the capture process, metadata related to capture may be generated.

For capture, a special camera for VR may be used. When 360 video for a virtual space generated using a computer is provided according to an embodiment, capture using a camera may not be performed. In this case, the capture process may be replaced by a process of simply generating related data.

The preparation process may be a process of processing the captured images/videos and metadata generated in the capture process. The captured images/videos may be subjected to stitching, projection, region-wise packing and/or encoding in the preparation process.

First, the images/videos may pass through a stitching process. The stitching process may be a process of connecting the captured images/videos to create a single panorama image/video or a spherical image/video.

Then, the stitched images/videos may pass through a projection process. In the projection process, the stitched images/videos can be projected onto a 2D image. This 2D image may be called a 2D image frame. Projection on a 2D image may be represented as mapping to the 2D image. The projected image/video data can have a form of a 2D image t1020 as shown in the figure.

The video data projected onto the 2D image can pass through a region-wise packing process in order to increase video coding efficiency. Region-wise packing may refer to a process of dividing the video data projected onto the 2D image into regions and processing the regions. Here, regions may refer to regions obtained by dividing a 2D image on which 360 video data is projected. Such regions may be obtained by dividing the 2D image equally or randomly according to an embodiment. Regions may be divided depending on a projection scheme according to an embodiment. The region-wise packing process is an optional process and thus may be omitted in the preparation process.

According to an embodiment, this process may include a process of rotating the regions or rearranging the regions on the 2D image in order to increase video coding efficiency. For example, the regions can be rotated such that specific sides of regions are positioned in proximity to each other to increase coding efficiency.

According to an embodiment, this process may include a process of increasing or decreasing the resolution of a specific region in order to differentiate the resolution for regions of the 360 video. For example, the resolution of regions corresponding to a relatively important part of the 360 video can be increased to higher than other regions. The video data projected onto the 2D image or the region-wise packed video data can pass through an encoding process using a video codec.

According to an embodiment, the preparation process may additionally include an editing process. In the editing process, the image/video data before or after projection may be edited. In the preparation process, metadata with respect to stitching/projection/encoding/editing may be generated. In addition, metadata with respect to the initial viewpoint or ROI (region of interest) of the video data projected onto the 2D image may be generated.

The transmission process may be a process of processing and transmitting the image/video data and metadata which have passed through the preparation process. For transmission, processing according to an arbitrary transmission protocol may be performed. The data that has been processed for transmission may be delivered over a broadcast network and/or broadband. The data may be delivered to a reception side in an on-demand manner. The reception side may receive the data through various paths.

The processing process refers to a process of decoding the received data and re-projecting the projected image/video data on a 3D model. In this process, the image/video data projected onto the 2D image may be re-projected onto a 3D space. This process may be called mapping projection. Here, the 3D space on which the data is mapped may have a form depending on a 3D model. For example, 3D models may include a sphere, a cube, a cylinder and a pyramid.

According to an embodiment, the processing process may further include an editing process, an up-scaling process, etc. In the editing process, the image/video data before or after re-projection can be edited. When the image/video data has been reduced, the size of the image/video data can be increased through up-scaling of samples in the up-scaling process. As necessary, the size may be decreased through down-scaling.

The rendering process may refer to a process of rendering and displaying the image/video data re-projected onto the 3D space. Re-projection and rendering may be collectively represented as rendering on a 3D model. The image/video re-projected (or rendered) on the 3D model may have a form t1030 as shown in the figure. The form t1030 corresponds to a case in which the image/video data is re-projected onto a spherical 3D model. A user can view a region of the rendered image/video through a VR display or the like. Here, the region viewed by the user may have a form t1040 shown in the figure.

The feedback process may refer to a process of delivering various types of feedback information which can be acquired in the display process to a transmission side. Through the feedback process, interactivity in 360 video consumption can be provided. According to an embodiment, head orientation information, viewport information indicating a region currently viewed by a user, etc. can be delivered to the transmission side in the feedback process. According to an embodiment, the user may interact with content realized in a VR environment. In this case, information related to the interaction may be delivered to the transmission side or a service provider in the feedback process. According to an embodiment, the feedback process may not be performed.

The head orientation information may refer to information about the position, angle and motion of a user's head. On the basis of this information, information about a region of 360 video currently viewed by the user, that is, viewport information can be calculated.

The viewport information may be information about a region of 360 video currently viewed by a user. Gaze analysis may be performed using the viewport information to check a manner in which the user consumes 360 video, a region of the 360 video at which the user gazes, and how long the user gazes at the region. Gaze analysis may be performed by the reception side and the analysis result may be delivered to the transmission side through a feedback channel. A device such as a VR display may extract a viewport region on the basis of the position/direction of a user's head, vertical or horizontal FOV supported by the device, etc.

According to an embodiment, the aforementioned feedback information may be consumed at the reception side as well as being delivered to the transmission side. That is, decoding, re-projection and rendering processes of the reception side can be performed using the aforementioned feedback information. For example, only 360 video corresponding to the region currently viewed by the user can be preferentially decoded and rendered using the head orientation information and/or the viewport information.

Here, a viewport or a viewport region can refer to a region of 360 video currently viewed by a user. A viewpoint is a point in 360 video which is viewed by the user and may refer to a center point of a viewport region. That is, a viewport is a region based on a viewpoint, and the size and form of the region can be determined by FOV (field of view) which will be described below.

In the above-described architecture for providing 360 video, image/video data which is subjected to a series of capture/projection/encoding/transmission/decoding/re-projection/rendering processes can be called 360 video data. The term “360 video data” may be used as the concept including metadata or signaling information related to such image/video data.

FIG. 2 illustrates a 360 video transmission device according to one aspect of the present invention.

According to one aspect, the present invention may relate to a 360 video transmission device. The 360 video transmission device according to the present invention may perform operations related to the above-described preparation process to the transmission process. The 360 video transmission device according to the present invention may include a data input unit, a stitcher, a projection processor, a region-wise packing processor (not shown), a metadata processor, a (transmission side) feedback processor, a data encoder, an encapsulation processor, a transmission processor and/or a transmitter as internal/external elements.

The data input unit may receive captured images/videos for respective viewpoints. The images/videos for the viewpoints may be images/videos captured by one or more cameras. In addition, the data input unit may receive metadata generated in the capture process. The data input unit may deliver the received images/videos for the viewpoints to the stitcher and deliver the metadata generated in the capture process to a signaling processor.

The stitcher may stitch the captured images/videos for the viewpoints. The stitcher may deliver the stitched 360 video data to the projection processor. The stitcher may receive necessary metadata from the metadata processor and use the metadata for stitching operation as necessary. The stitcher may deliver the metadata generated in the stitching process to the metadata processor. The metadata in the stitching process may include information indicating whether stitching has been performed, a stitching type, etc.

The projection processor may project the stitched 360 video data on a 2D image. The projection processor may perform projection according to various schemes which will be described below. The projection processor may perform mapping in consideration of the depth of 360 video data for each viewpoint. The projection processor may receive metadata necessary for projection from the metadata processor and use the metadata for the projection operation as necessary. The projection processor may deliver metadata generated in the projection process to the metadata processor. The metadata of the projection process may include a projection scheme type.

The region-wise packing processor (not shown) may perform the aforementioned region-wise packing process. That is, the region-wise packing processor may perform a process of dividing the projected 360 video data into regions, rotating or rearranging the regions or changing the resolution of each region. As described above, the region-wise packing process is an optional process, and when region-wise packing is not performed, the region-wise packing processor can be omitted. The region-wise packing processor may receive metadata necessary for region-wise packing from the metadata processor and use the metadata for the region-wise packing operation as necessary. The metadata of the region-wise packing processor may include a degree to which each region is rotated, the size of each region, etc.

The aforementioned stitcher, the projection processor and/or the region-wise packing processor may be realized by one hardware component according to an embodiment.

The metadata processor may process metadata which can be generated in the capture process, the stitching process, the projection process, the region-wise packing process, the encoding process, the encapsulation process and/or the processing process for transmission. The metadata processor may generate 360 video related metadata using such metadata. According to an embodiment, the metadata processor may generate the 360 video related metadata in the form of a signaling table. The 360 video related metadata may be called metadata or 360 video related signaling information according to context. Furthermore, the metadata processor may deliver acquired or generated metadata to internal elements of the 360 video transmission device as necessary. The metadata processor may deliver the 360 video related metadata to the data encoder, the encapsulation processor and/or the transmission processor such that the metadata can be transmitted to the reception side.

The data encoder may encode the 360 video data projected onto the 2D image and/or the region-wise packed 360 video data. The 360 video data may be encoded in various formats.

The encapsulation processor may encapsulate the encoded 360 video data and/or 360 video related metadata into a file. Here, the 360 video related metadata may be delivered from the metadata processor. The encapsulation processor may encapsulate the data in a file format such as ISOBMFF, CFF or the like or process the data into a DASH segment. The encapsulation processor may include the 360 video related metadata in a file format according to an embodiment. For example, the 360 video related metadata can be included in boxes of various levels in an ISOBMFF file format or included as data in an additional track in a file. The encapsulation processor may encapsulate the 360 video related metadata into a file according to an embodiment. The transmission processor may perform processing for transmission on the 360 video data encapsulated in a file format. The transmission processor may process the 360 video data according to an arbitrary transmission protocol. The processing for transmission may include processing for delivery through a broadcast network and processing for delivery over a broadband. According to an embodiment, the transmission processor may receive 360 video related metadata from the metadata processor in addition to the 360 video data and perform processing for transmission on the 360 video related metadata.

The transmission unit may transmit the processed 360 video data and/or the 360 video related metadata over a broadcast network and/or broadband. The transmission unit may include an element for transmission over a broadcast network and an element for transmission over a broadband.

According to an embodiment of the present invention, the 360 video transmission device may further include a data storage unit (not shown) as an internal/external element. The data storage unit may store the encoded 360 video data and/or 360 video related metadata before delivery to the transmission processor. Such data may be stored in a file format such as ISOBMFF. When 360 video is transmitted in real time, the data storage unit may not be used. However, 360 video is delivered on demand, in non-real time or over a broadband, encapsulated 360 data may be stored in the data storage unit for a predetermined period and then transmitted.

According to another embodiment of the present invention, the 360 video transmission device may further include a (transmission side) feedback processor and/or a network interface (not shown) as internal/external elements. The network interface may receive feedback information from a 360 video reception device according to the present invention and deliver the feedback information to the (transmission side) feedback processor. The feedback processor may deliver the feedback information to the stitcher, the projection processor, the region-wise packing processor, the data encoder, the encapsulation processor, the metadata processor and/or the transmission processor. The feedback information may be delivered to the metadata processor and then delivered to each internal element according to an embodiment. Upon reception of the feedback information, internal elements may reflect the feedback information in 360 video data processing.

According to another embodiment of the 360 video transmission device of the present invention, the region-wise packing processor may rotate regions and map the regions on a 2D image. Here, the regions may be rotated in different directions at different angles and mapped on the 2D image. The regions may be rotated in consideration of neighboring parts and stitched parts of the 360 video data on the spherical plane before projection. Information about rotation of the regions, that is, rotation directions and angles may be signaled using 360 video related metadata. According to another embodiment of the 360 video transmission device according to the present invention, the data encoder may perform encoding differently on respective regions. The data encoder may encode a specific region with high quality and encode other regions with low quality. The feedback processor at the transmission side may deliver the feedback information received from the 360 video reception device to the data encoder such that the data encoder can use encoding methods differentiated for regions. For example, the feedback processor can deliver viewport information received from the reception side to the data encoder. The data encoder may encode regions including a region indicated by the viewport information with higher quality (UHD) than other regions.

According to another embodiment of the 360 video transmission device according to the present invention, the transmission processor may perform processing for transmission differently on respective regions. The transmission processor may apply different transmission parameters (modulation orders, code rates, etc.) to regions such that data delivered for the regions have different robustnesses.

Here, the feedback processor may deliver the feedback information received from the 360 video reception device to the transmission processor such that the transmission processor can perform transmission processing differentiated for respective regions. For example, the feedback processor can deliver viewport information received from the reception side to the transmission processor. The transmission processor may perform transmission processing on regions including a region indicated by the viewport information such that the regions have higher robustness than other regions.

The aforementioned internal/external elements of the 360 video transmission device according to the present invention may be hardware elements. According to an embodiment, the internal/external elements may be modified, omitted, replaced by other elements or integrated with other elements. According to an embodiment, additional elements may be added to the 360 video transmission device.

FIG. 3 illustrates a 360 video reception device according to another aspect of the present invention.

According to another aspect, the present invention may relate to a 360 video reception device. The 360 video reception device according to the present invention may perform operations related to the above-described processing process and/or the rendering process. The 360 video reception device according to the present invention may include a reception unit, a reception processor, a decapsulation processor, a data decoder, a metadata parser, a (reception side) feedback processor, a re-projection processor and/or a renderer as internal/external elements.

The reception unit may receive 360 video data transmitted from the 360 video transmission device according to the present invention. The reception unit may receive the 360 video data through a broadcast network or a broadband depending on a transmission channel.

The reception processor may perform processing according to a transmission protocol on the received 360 video data. The reception processor may perform a reverse of the process of the transmission processor. The reception processor may deliver the acquired 360 video data to the decapsulation processor and deliver acquired 360 video related metadata to the metadata parser. The 360 video related metadata acquired by the reception processor may have a form of a signaling table.

The decapsulation processor may decapsulate the 360 video data in a file format received from the reception processor. The decapsulation processor may decapsulate files in ISOBMFF to acquire 360 video data and 360 video related metadata. The acquired 360 video data may be delivered to the data decoder and the acquired 360 video related metadata may be delivered to the metadata parser. The 360 video related metadata acquired by the decapsulation processor may have a form of box or track in a file format. The decapsulation processor may receive metadata necessary for decapsulation from the metadata parser as necessary.

The data decoder may decode the 360 video data. The data decoder may receive metadata necessary for decoding from the metadata parser. The 360 video related metadata acquired in the data decoding process may be delivered to the metadata parser.

The metadata parser may parse/decode the 360 video related metadata. The metadata parser may deliver the acquired metadata to the data decapsulation processor, the data decoder, the re-projection processor and/or the renderer.

The re-projection processor may re-project the decoded 360 video data. The re-projection processor may re-project the 360 video data on a 3D space. The 3D space may have different forms depending on used 3D models. The re-projection processor may receive metadata necessary for re-projection from the metadata parser. For example, the re-projection processor may receive information about the type of a used 3D model and detailed information thereof from the metadata parser. According to an embodiment, the re-projection processor may re-project only 360 video data corresponding to a specific region on the 3D space using the metadata necessary for re-projection.

The renderer may render the re-projected 360 video data. This may be represented as rendering of the 360 video data on a 3D space as described above. When two processes are simultaneously performed in this manner, the re-projection processor and the renderer may be integrated and the processes may be performed in the renderer. According to an embodiment, the renderer may render only a region viewed by the user according to view information of the user.

The user may view part of the rendered 360 video through a VR display. The VR display is a device for reproducing 360 video and may be included in the 360 video reception device (tethered) or connected to the 360 video reception device as a separate device (un-tethered).

According to an embodiment of the present invention, the 360 video reception device may further include a (reception side) feedback processor and/or a network interface (not shown) as internal/external elements. The feedback processor may acquire feedback information from the renderer, the re-projection processor, the data decoder, the decapsulation processor and/or the VR display and process the feedback information. The feedback information may include viewport information, head orientation information, gaze information, etc. The network interface may receive the feedback information from the feedback processor and transmit the same to the 360 video transmission device.

As described above, the feedback information may be used by the reception side in addition to being delivered to the transmission side. The reception side feedback processor can deliver the acquired feedback information to internal elements of the 360 video reception device such that the feedback information is reflected in a rendering process. The reception side feedback processor can deliver the feedback information to the renderer, the re-projection processor, the data decoder and/or the decapsulation processor. For example, the renderer can preferentially render a region viewed by the user using the feedback information. In addition, the decapsulation processor and the data decoder can preferentially decapsulate and decode a region viewed by the user or a region to be viewed by the user.

The internal/external elements of the 360 video reception device according to the present invention may be hardware elements. According to an embodiment, the internal/external elements may be modified, omitted, replaced by other elements or integrated with other elements. According to an embodiment, additional elements may be added to the 360 video reception device.

Another aspect of the present invention may relate to a method of transmitting 360 video and a method of receiving 360 video. The methods of transmitting/receiving 360 video according to the present invention may be performed by the above-described 360 video transmission/reception devices or embodiments thereof.

The aforementioned embodiments of the 360 video transmission/reception devices and embodiments of the internal/external elements thereof may be combined. For example, embodiments of the projection processor and embodiments of the data encoder can be combined to create as many embodiments of the 360 video transmission device as the number of the embodiments. The combined embodiments are also included in the scope of the present invention.

FIG. 4 illustrates a 360 video transmission device/360 video reception device according to another embodiment of the present invention.

As described above, 360 content may be provided according to the architecture shown in (a). The 360 content may be provided in the form of a file or in the form of a segment based download or streaming service such as DASH. Here, the 360 content may be called VR content.

As described above, 360 video data and/or 360 audio data may be acquired.

The 360 audio data may be subjected to audio preprocessing and audio encoding. Through these processes, audio related metadata may be generated, and the encoded audio and audio related metadata may be subjected to processing for transmission (file/segment encapsulation).

The 360 video data may pass through the aforementioned processes. The stitcher of the 360 video transmission device may stitch the 360 video data (visual stitching). This process may be omitted and performed at the reception side according to an embodiment. The projection processor of the 360 video transmission device may project the 360 video data on a 2D image (projection and mapping (packing)).

The stitching and projection processes are shown in (b) in detail. In (b), when the 360 video data (input images) is delivered, stitching and projection may be performed thereon. The projection process may be regarded as projecting the stitched 360 video data on a 3D space and arranging the projected 360 video data on a 2D image. In the specification, this process may be represented as projecting the 360 video data on a 2D image. Here, the 3D space may be a sphere or a cube. The 3D space may be identical to the 3D space used for re-projection at the reception side.

The 2D image may also be called a projected frame C. Region-wise packing may be optionally performed on the 2D image. When region-wise packing is performed, the positions, forms and sizes of regions may be indicated such that the regions on the 2D image can be mapped on a packed frame D. When region-wise packing is not performed, the projected frame may be identical to the packed frame. Regions will be described below. The projection process and the region-wise packing process may be represented as projecting regions of the 360 video data on a 2D image. The 360 video data may be directly converted into the packed frame without an intermediate process according to design.

In (a), the projected 360 video data may be image-encoded or video-encoded. Since the same content may be present for different viewpoints, the same content may be encoded into different bit streams. The encoded 360 video data may be processed into a file format such as ISOBMFF according to the aforementioned encapsulation processor. Alternatively, the encapsulation processor may process the encoded 360 video data into segments. The segments may be included in an individual track for DASH based transmission.

Along with processing of the 360 video data, 360 video related metadata may be generated as described above. This metadata may be included in a video bitstream or a file format and delivered. The metadata may be used for encoding, file format encapsulation, processing for transmission, etc.

The 360 audio/video data may pass through processing for transmission according to the transmission protocol and then be transmitted. The aforementioned 360 video reception device may receive the 360 audio/video data over a broadcast network or broadband.

In (a), a VR service platform may correspond to an embodiment of the aforementioned 360 video reception device. In (a), loudspeakers/headphones, display and head/eye tracking components are performed by an external device or a VR application of the 360 video reception device. According to an embodiment, the 360 video reception device may include all of these components. According to an embodiment, the head/eye tracking components may correspond to the aforementioned reception side feedback processor.

The 360 video reception device may perform processing for reception (file/segment decapsulation) on the 360 audio/video data. The 360 audio data may be subjected to audio decoding and audio rendering and then provided to the user through a speaker/headphone.

The 360 video data may be subjected to image decoding or video decoding and visual rendering and provided to the user through a display. Here, the display may be a display supporting VR or a normal display.

As described above, the rendering process may be regarded as a process of re-projecting 360 video data on a 3D space and rendering the re-projected 360 video data. This may be represented as rendering of the 360 video data on the 3D space.

The head/eye tracking components may acquire and process head orientation information, gaze information and viewport information of a user. This has been described above.

The reception side may include a VR application which communicates with the aforementioned processes of the reception side.

FIG. 5 illustrates the concept of aircraft principal axes for describing a 3D space of the present invention.

In the present invention, the concept of aircraft principal axes may be used to represent a specific point, position, direction, spacing and region in a 3D space.

That is, the concept of aircraft principal axes may be used to describe a 3D space before projection or after re-projection and to signal the same. According to an embodiment, a method using X, Y and Z axes or a spherical coordinate system may be used.

An aircraft can feely rotate in the three dimension. Axes which form the three dimension are called pitch, yaw and roll axes. In the specification, these may be represented as pitch, yaw and roll or a pitch direction, a yaw direction and a roll direction.

The pitch axis may refer to a reference axis of a direction in which the front end of the aircraft rotates up and down. In the shown concept of aircraft principal axes, the pitch axis can refer to an axis connected between wings of the aircraft.

The yaw axis may refer to a reference axis of a direction in which the front end of the aircraft rotates to the left/right. In the shown concept of aircraft principal axes, the yaw axis can refer to an axis connected from the top to the bottom of the aircraft.

The roll axis may refer to an axis connected from the front end to the tail of the aircraft in the shown concept of aircraft principal axes, and rotation in the roll direction can refer to rotation based on the roll axis.

As described above, a 3D space in the present invention can be described using the concept of the pitch, yaw and roll.

FIG. 6 illustrates projection schemes according to an embodiment of the present invention.

As described above, the projection processor of the 360 video transmission device according to the present invention may project stitched 360 video data on a 2D image. In this process, various projection schemes can be used.

According to another embodiment of the 360 video transmission device according to the present invention, the projection processor may perform projection using a cubic projection scheme. For example, stitched video data can be represented on a spherical plane. The projection processor may segment the 360 video data into faces of a cube and project the same on the 2D image. The 360 video data on the spherical plane may correspond to the faces of the cube and be projected onto the 2D image as shown in (a).

According to another embodiment of the 360 video transmission device according to the present invention, the projection processor may perform projection using a cylindrical projection scheme. Similarly, if stitched video data can be represented on a spherical plane, the projection processor can segment the 360 video data into parts of a cylinder and project the same on the 2D image. The 360 video data on the spherical plane can correspond to the side, top and bottom of the cylinder and be projected onto the 2D image as shown in (b).

According to another embodiment of the 360 video transmission device according to the present invention, the projection processor may perform projection using a pyramid projection scheme. Similarly, if stitched video data can be represented on a spherical plane, the projection processor can regard the 360 video data as a pyramid form, segment the 360 video data into faces of the pyramid and project the same on the 2D image. The 360 video data on the spherical plane can correspond to the front, left top, left bottom, right top and right bottom of the pyramid and be projected onto the 2D image as shown in (c).

According to an embodiment, the projection processor may perform projection using an equirectangular projection scheme and a panoramic projection scheme in addition to the aforementioned schemes.

As described above, regions may refer to regions obtained by dividing a 2D image on which 360 video data is projected. Such regions need not correspond to respective faces of the 2D image projected according to a projection scheme. However, regions may be divided such that the faces of the projected 2D image correspond to the regions and region-wise packing may be performed according to an embodiment. Regions may be divided such that a plurality of faces may correspond to one region or one face may correspond to a plurality of regions according to an embodiment. In this case, the regions may depend on projection schemes. For example, the top, bottom, front, left, right and back sides of the cube can be respective regions in (a). The side, top and bottom of the cylinder can be respective regions in (b). The front, left top, left bottom, right top and right bottom sides of the pyramid can be respective regions in (c).

FIG. 7 illustrates tiles according to an embodiment of the present invention.

360 video data projected onto a 2D image or region-wise packed 360 video data may be divided into one or more tiles. (a) shows that one 2D image is divided into 16 tiles. Here, the 2D image may be the aforementioned projected frame or packed frame. According to another embodiment of the 360 video transmission device of the present invention, the data encoder may independently encode the tiles.

The aforementioned region-wise packing can be discriminated from tiling. The aforementioned region-wise packing may refer to a process of dividing 360 video data projected onto a 2D image into regions and processing the regions in order to increase coding efficiency or adjusting resolution. Tiling may refer to a process through which the data encoder divides a projected frame or a packed frame into tiles and independently encode the tiles. When 360 video is provided, a user does not simultaneously use all parts of the 360 video. Tiling enables only tiles corresponding to important part or specific part, such as a viewport currently viewed by the user, to be transmitted to or consumed by the reception side on a limited bandwidth. Through tiling, a limited bandwidth can be used more efficiently and the reception side can reduce computational load compared to a case in which the entire 360 video data is processed simultaneously.

A region and a tile are discriminated from each other and thus they need not be identical. However, a region and a tile may refer to the same area according to an embodiment. Region-wise packing may be performed based on tiles and thus regions can correspond to tiles according to an embodiment. Furthermore, when sides according to a projection scheme correspond to regions, each side, region and tile according to the projection scheme may refer to the same area according to an embodiment. A region may be called a VR region and a tile may be called a tile region according to context.

ROI (Region of Interest) may refer to a region of interest of users, which is provided by a 360 content provider. When the 360 content provider produces 360 video, the 360 content provider can produce the 360 video in consideration of a specific region which is expected to be a region of interest of users. According to an embodiment, ROI may correspond to a region in which important content of the 360 video is reproduced.

According to another embodiment of the 360 video transmission/reception devices of the present invention, the reception side feedback processor may extract and collect viewport information and deliver the same to the transmission side feedback processor. In this process, the viewport information can be delivered using network interfaces of both sides. In the 2D image shown in (a), a viewport t6010 is displayed. Here, the viewport may be displayed over nine tiles of the 2D images.

In this case, the 360 video transmission device may further include a tiling system. According to an embodiment, the tiling system may be located following the data encoder (b), may be included in the aforementioned data encoder or transmission processor, or may be included in the 360 video transmission device as a separate internal/external element.

The tiling system may receive viewport information from the transmission side feedback processor. The tiling system may select only tiles included in a viewport region and transmit the same. In the 2D image shown in (a), only nine tiles including the viewport region t6010 among 16 tiles can be transmitted. Here, the tiling system may transmit tiles in a unicast manner over a broadband because the viewport region is different for users.

In this case, the transmission side feedback processor may deliver the viewport information to the data encoder. The data encoder may encode the tiles including the viewport region with higher quality than other tiles.

Furthermore, the transmission side feedback processor may deliver the viewport information to the metadata processor. The metadata processor may deliver metadata related to the viewport region to each internal element of the 360 video transmission device or include the metadata in 360 video related metadata.

By using this tiling method, transmission bandwidths can be saved and processes differentiated for tiles can be performed to achieve efficient data processing/transmission.

The above-described embodiments related to the viewport region can be applied to specific regions other than the viewport region in a similar manner. For example, the aforementioned processes performed on the viewport region can be performed on a region determined to be a region in which users are interested through the aforementioned gaze analysis, ROI, and a region (initial view, initial viewpoint) initially reproduced when a user views 360 video through a VR display.

According to another embodiment of the 360 video transmission device of the present invention, the transmission processor may perform processing for transmission differently on tiles. The transmission processor may apply different transmission parameters (modulation orders, code rates, etc.) to tiles such that data delivered for the tiles has different robustnesses.

Here, the transmission side feedback processor may deliver feedback information received from the 360 video reception device to the transmission processor such that the transmission processor can perform transmission processing differentiated for tiles. For example, the transmission side feedback processor can deliver the viewport information received from the reception side to the transmission processor. The transmission processor can perform transmission processing such that tiles including the corresponding viewport region have higher robustness than other tiles.

FIG. 8 illustrates 360 video related metadata according to an embodiment of the present invention.

The aforementioned 360 video related metadata may include various types of metadata related to 360 video. The 360 video related metadata may be called 360 video related signaling information according to context. The 360 video related metadata may be included in an additional signaling table and transmitted, included in a DASH MPD and transmitted, or included in a file format such as ISOBMFF in the form of box and delivered. When the 360 video related metadata is included in the form of box, the 360 video related metadata may be included in various levels such as a file, fragment, track, sample entry, sample, etc. and may include metadata about data of the corresponding level.

According to an embodiment, part of the metadata, which will be described below, may be configured in the form of a signaling table and delivered, and the remaining part may be included in a file format in the form of a box or a track.

According to an embodiment of the 360 video related metadata, the 360 video related metadata may include basic metadata related to a projection scheme, stereoscopic related metadata, initial view/initial viewpoint related metadata, ROI related metadata, FOV (Field of View) related metadata and/or cropped region related metadata. According to an embodiment, the 360 video related metadata may include additional metadata in addition to the aforementioned metadata.

Embodiments of the 360 video related metadata according to the present invention may include at least one of the aforementioned basic metadata, stereoscopic related metadata, initial view/initial viewpoint related metadata, ROI related metadata, FOV related metadata, cropped region related metadata and/or additional metadata. Embodiments of the 360 video related metadata according to the present invention may be configured in various manners depending on the number of cases of metadata included therein. According to an embodiment, the 360 video related metadata may further include additional metadata in addition to the aforementioned metadata.

The basic metadata may include 3D model related information, projection scheme related information and the like. The basic metadata may include a vr_geometry field, a projection_scheme field, etc. According to an embodiment, the basic metadata may further include additional information.

The vr_geometry field can indicate the type of a 3D model supported by the corresponding 360 video data. When the 360 video data is re-projected onto a 3D space as described above, the 3D space may have a form according to a 3D model indicated by the vr_geometry field. According to an embodiment, a 3D model used for rendering may differ from the 3D model used for re-projection, indicated by the vr_geometry field. In this case, the basic metadata may further include a field which indicates the 3D model used for rendering. When the field has values of 0, 1, 2 and 3, the 3D space can conform to 3D models of a sphere, a cube, a cylinder and a pyramid. When the field has the remaining values, the field can be reserved for future use. According to an embodiment, the 360 video related metadata may further include detailed information about the 3D model indicated by the field. Here, the detailed information about the 3D model may refer to the radius of a sphere, the height of a cylinder, etc. for example. This field may be omitted.

The projection_scheme field can indicate a projection scheme used when the 360 video data is projected onto a 2D image. When the field has values of 0, 1, 2, 3, 4, and 5, the field indicates that the equirectangular projection scheme, cubic projection scheme, cylindrical projection scheme, tile-based projection scheme, pyramid projection scheme and panoramic projection scheme are used. When the field has a value of 6, the field indicates that the 360 video data is directly projected onto the 2D image without stitching. When the field has the remaining values, the field can be reserved for future use. According to an embodiment, the 360 video related metadata may further include detailed information about regions generated according to a projection scheme specified by the field. Here, the detailed information about regions may refer to information indicating whether regions have been rotated, the radius of the top region of a cylinder, etc. for example.

The stereoscopic related metadata may include information about 3D related attributes of the 360 video data. The stereoscopic related metadata may include an is_stereoscopic field and/or a stereo_mode field. According to an embodiment, the stereoscopic related metadata may further include additional information.

The is_stereoscopic field can indicate whether the 360 video data supports 3D. When the field is 1, the 360 video data supports 3D. When the field is 0, the 360 video data does not support 3D. This field may be omitted.

The stereo_mode field can indicate 3D layout supported by the corresponding 360 video. Whether the 360 video supports 3D can be indicated only using this field. In this case, the is_stereoscopic field can be omitted. When the field is 0, the 360 video may be a mono mode. That is, the projected 2D image can include only one mono view. In this case, the 360 video may not support 3D.

When this field is set to 1 and 2, the 360 video can conform to left-right layout and top-bottom layout. The left-right layout and top-bottom layout may be called a side-by-side format and a top-bottom format. In the case of the left-right layout, 2D images on which left image/right image are projected can be positioned at the left/right on an image frame. In the case of the top-bottom layout, 2D images on which left image/right image are projected can be positioned at the top/bottom on an image frame. When the field has the remaining values, the field can be reserved for future use.

The initial view/initial viewpoint related metadata may include information about a view (initial view) which is viewed by a user when initially reproducing 360 video. The initial view/initial viewpoint related metadata may include an initial_view_yaw_degree field, an initial_view_pitch_degree field and/or an initial_view_roll_degree field. According to an embodiment, the initial view/initial viewpoint related metadata may further include additional information.

The initial_view_yaw_degree field, initial_view_pitch_degree field and initial_view_roll_degree field can indicate an initial view when the 360 video is reproduced. That is, the center point of a viewport which is initially viewed when the 360 video is reproduced can be indicated by these three fields. The fields can indicate the center point using a direction (sign) and a degree (angle) of rotation on the basis of yaw, pitch and roll axes. Here, the viewport which is initially viewed when the 360 video is reproduced according to FOV. The width and height of the initial viewport based on the indicated initial view may be determined through FOV. That is, the 360 video reception device can provide a specific region of the 360 video as an initial viewport to a user using the three fields and FOV information.

According to an embodiment, the initial view indicated by the initial view/initial viewpoint related metadata may be changed per scene. That is, scenes of the 360 video change as 360 content proceeds with time. The initial view or initial viewport which is initially viewed by a user can change for each scene of the 360 video. In this case, the initial view/initial viewpoint related metadata can indicate the initial view per scene. To this end, the initial view/initial viewpoint related metadata may further include a scene identifier for identifying a scene to which the initial view is applied. In addition, since FOV may change per scene of the 360 video, the initial view/initial viewpoint related metadata may further include FOV information per scene which indicates FOV corresponding to the relative scene.

The ROI related metadata may include information related to the aforementioned ROI. The ROI related metadata may include a 2d_roi_range_flag field and/or a 3d_roi_range_flag field. These two fields can indicate whether the ROI related metadata includes fields which represent ROI on the basis of a 2D image or fields which represent ROI on the basis of a 3D space. According to an embodiment, the ROI related metadata may further include additional information such as differentiate encoding information depending on ROI and differentiate transmission processing information depending on ROI.

When the ROI related metadata includes fields which represent ROI on the basis of a 2D image, the ROI related metadata may include a min_top_left_x field, a max_top_left_x field, a min_top_left_y field, a max_top_left_y field, a min_width field, a max_width field, a min_height field, a max_height field, a min_x field, a max_x field, a min_y field and/or a max_y field.

The min_top_left_x field, max_top_left_x field, min_top_left_y field, max_top_left_y field can represent minimum/maximum values of the coordinates of the left top end of the ROI. These fields can sequentially indicate a minimum x coordinate, a maximum x coordinate, a minimum y coordinate and a maximum y coordinate of the left top end.

The min_width field, max_width field, min_height field and max_height field can indicate minimum/maximum values of the width and height of the ROI. These fields can sequentially indicate a minimum value and a maximum value of the width and a minimum value and a maximum value of the height.

The min_x field, max_x field, min_y field and max_y field can indicate minimum and maximum values of coordinates in the ROI. These fields can sequentially indicate a minimum x coordinate, a maximum x coordinate, a minimum y coordinate and a maximum y coordinate of coordinates in the ROI. These fields can be omitted.

When ROI related metadata includes fields which indicate ROI on the basis of coordinates on a 3D rendering space, the ROI related metadata may include a min_yaw field, a max_yaw field, a min_pitch field, a max_pitch field, a min_roll field, a max_roll field, a min_field_of_view field and/or a max_field_of_view field.

The min_yaw field, max_yaw field, min_pitch field, max_pitch field, min_roll field and max_roll field can indicate a region occupied by ROI on a 3D space using minimum/maximum values of yaw, pitch and roll. These fields can sequentially indicate a minimum value of yaw-axis based reference rotation amount, a maximum value of yaw-axis based reference rotation amount, a minimum value of pitch-axis based reference rotation amount, a maximum value of pitch-axis based reference rotation amount, a minimum value of roll-axis based reference rotation amount, and a maximum value of roll-axis based reference rotation amount.

The min_field_of_view field and max_field_of_view field can indicate minimum/maximum values of FOV of the corresponding 360 video data. FOV can refer to the range of view displayed at once when 360 video is reproduced. The min_field_of_view field and max_field_of_view field can indicate minimum and maximum values of FOV. These fields can be omitted. These fields may be included in FOV related metadata which will be described below.

The FOV related metadata may include the aforementioned FOV related information. The FOV related metadata may include a content_fov_flag field and/or a content_fov field. According to an embodiment, the FOV related metadata may further include additional information such as the aforementioned minimum/maximum value related information of FOV.

The content_fov_flag field can indicate whether corresponding 360 video includes information about FOV intended when the 360 video is produced. When this field value is 1, a content_fov field can be present.

The content_fov field can indicate information about FOV intended when the 360 video is produced. According to an embodiment, a region displayed to a user at once in the 360 video can be determined according to vertical or horizontal FOV of the 360 video reception device. Alternatively, a region displayed to a user at once in the 360 video may be determined by reflecting FOV information of this field according to an embodiment.

Cropped region related metadata may include information about a region including 360 video data in an image frame. The image frame may include a 360 video data projected active video area and other areas. Here, the active video area can be called a cropped region or a default display region. The active video area is viewed as 360 video on an actual VR display and the 360 video reception device or the VR display can process/display only the active video area. For example, when the aspect ratio of the image frame is 4:3, only an area of the image frame other than an upper part and a lower part of the image frame can include 360 video data. This area can be called the active video area.

The cropped region related metadata can include an is_cropped_region field, a cr_region_left_top_x field, a cr_region_left_top_y field, a cr_region_width field and/or a cr_region_height field. According to an embodiment, the cropped region related metadata may further include additional information.

The is_cropped_region field may be a flag which indicates whether the entire area of an image frame is used by the 360 video reception device or the VR display. That is, this field can indicate whether the entire image frame indicates an active video area. When only part of the image frame is an active video area, the following four fields may be added.

A cr_region_left_top_x field, a cr_region_left_top_y field, a cr_region_width field and a cr_region_height field can indicate an active video area in an image frame. These fields can indicate the x coordinate of the left top, the y coordinate of the left top, the width and the height of the active video area. The width and the height can be represented in units of pixel.

As described above, 360-degree video related signaling information or metadata can be included in an arbitrarily defined signaling table, included in the form of box in a file format such as ISOBMFF or common file format or included in a DASH MPD and transmitted. In addition, 360-degree media data may be included in such a file format or a DASH segment and transmitted.

The ISOBMFF and DASH MPD will be sequentially described below.

FIG. 9 illustrates a media file structure according to one embodiment of the present invention.

FIG. 10 illustrates a hierarchical structure of boxes in ISOBMFF according to one embodiment of the present invention.

To store and transmit media data such as audio or video, a standardized media file format can be defined. According to an embodiment, a media file may have a file format based on ISO base media file format (ISOBMFF).

A media file according to the present invention may include at least one box. Here, a box may be a data block or an object including media data or metadata related to media data. Boxes may be arranged in a hierarchical structure, and thus data can be classified and a media file can take a form suitable for storage and/or transmission of media data. In addition, the media file may have a structure which facilitates accessing media information such as user moving to a specific point in media content.

The media file according to the present invention can include an ftyp box, a moov box and/or an mdat box.

The ftyp box (file type box) can provide information related to file type or compatibility of the corresponding media file. The ftyp box can include configuration version information about media data of the media file. A decoder can identify the corresponding media file with reference to the ftyp box.

The moov box (movie box) may include metadata about the media data of the media file. The moov box can serve as a container for all pieces of metadata. The moov box may be a box at the highest level among metadata related boxes. According to an embodiment, only one moov box may be included in the media file.

The mdat box (media data box) may contain actual media data of the corresponding media file. The media data can include audio samples and/or video samples and the mdat box can serve as a container for containing such media samples.

According to an embodiment, the moov box may include an mvhd box, a trak box and/or an mvex box as lower boxes.

The mvhd box (movie header box) can include media presentation related information of media data included in the corresponding media file. That is, the mvhd box can include information such as a media generation time, change time, time standard and period of corresponding media presentation.

The trak box (track box) can provide information related to a track of corresponding media data. The trak box can include information such as stream related information about an audio track or a video track, presentation related information, and access related information. A plurality of trak boxes may be provided depending on the number of tracks.

The trak box may include a tkhd box (track header box) as a lower box according to an embodiment. The tkhd box can include information about a track indicated by the trak box. The tkhd box can include information such as a generation time, change time and track identifier of the corresponding track.

The mvex box (movie extend box) can indicate that the corresponding media file may include a moof box which will be described below. Moov boxes may need to be scanned to recognize all media samples of a specific track.

The media file according to the present invention may be divided into a plurality of fragments according to an embodiment (t18010). Accordingly, the media file can be segmented and stored or transmitted. Media data (mdat box) of the media file is divided into a plurality of fragments and each fragment can include the moof box and divided mdat boxes. According to an embodiment, information of the ftyp box and/or the moov box may be necessary to use fragments.

The moof box (movie fragment box) can provide metadata about media data of a corresponding fragment. The moof box may be a box at the highest layer among boxes related to the metadata of the corresponding fragment.

The mdat box (media data box) can include actual media data as described above. The mdat box can include media samples of media data corresponding to each fragment.

According to an embodiment, the aforementioned moof box can include an mfhd box and/or a traf box as lower boxes.

The mfhd box (movie fragment header box) can include information related to correlation of divided fragments. The mfhd box can include a sequence number to indicate the order of the media data of the corresponding fragment. In addition, it is possible to check whether there is omitted data among divided data using the mfhd box.

The traf box (track fragment box) can include information about a corresponding track fragment. The traf box can provide metadata about a divided track fragment included in the corresponding fragment. The traf box can provide metadata for decoding/reproducing media samples in the corresponding track fragment. A plurality of traf boxes may be provided depending on the number of track fragments.

According to an embodiment, the aforementioned traf box may include a tfhd box and/or a trun box as lower boxes.

The tfhd box (track fragment header box) can include header information of the corresponding track fragment. The tfhd box can provide information such as a basic sample size, period, offset and identifier for media samples of the track fragment indicated by the aforementioned traf box.

The trun box (track fragment run box) can include information related to the corresponding track fragment. The trun box can include information such as a period, size and reproduction timing of each media sample.

The aforementioned media file and fragments of the media file can be processed into segments and transmitted. Segments may include an initialization segment and/or a media segment.

A file of an embodiment t18020 shown in the figure may be a file including information related to initialization of a media decoder except media data. This file can correspond to the aforementioned initialization segment. The initialization segment can include the aforementioned ftyp box and/or the moov box.

The file of an embodiment t18030 shown in the figure may be a file including the aforementioned fragments. For example, this file can correspond to the aforementioned media segment. The media segment can include the aforementioned moof box and/or mdat box. In addition, the media segment can further include an styp box and/or an sidx box.

The styp box (segment type box) can provide information for identifying media data of a divided fragment. The styp box can perform the same role as the aforementioned ftyp box for a divided fragment. According to an embodiment, the styp box can have the same format as the ftyp box.

The sidx box (segment index box) can provide information indicating an index for a divided fragment. Accordingly, the sidx box can indicate the order of the divided fragment.

An ssix box may be further provided according to an embodiment t18040. The ssix box (sub-segment index box) can provide information indicating indexes of sub-segments when a segment is divided into the sub-segments.

Boxes in a media file may further include extended information on the basis of a box as shown in an embodiment t18050 or a full box. In this embodiment, a size field and a largesize field can indicate the length of a corresponding box in bytes. A version field can indicate the version of a corresponding box format. A type field can indicate the type or identifier of the corresponding box. A flags field can indicate flags related to the corresponding box.

FIG. 11 illustrates overall operation of a DASH based adaptive streaming model according to an embodiment of the present invention.

A DASH based adaptive streaming model according to an embodiment t50010 shown in the figure describes operations between an HTTP server and a DASH client. Here, DASH (dynamic adaptive streaming over HTTP) is a protocol for supporting HTTP based adaptive streaming and can dynamically support streaming depending on network state. Accordingly, reproduction of AV content can be seamlessly provided.

First, the DASH client can acquire an MPD. The MPD can be delivered from a service provider such as the HTTP server. The DASH client can request segments described in the MPD from the server using information for accessing the segments. The request can be performed based on a network state.

The DASH client can acquire the segments, process the segments in a media engine and display the processed segments on a screen. The DASH client can request and acquire necessary segments by reflecting a presentation time and/or a network state in real time (adaptive streaming). Accordingly, content can be seamlessly presented.

The MPD (media presentation description) is a file including detained information used for the DASH client to dynamically acquire segments and can be represented in XML.

A DASH client controller can generate a command for requesting the MPD and/or segments on the basis of a network state. In addition, the DASH client controller can control an internal block such as the media engine to use acquired information.

An MPD parser can parse the acquired MPD in real time. Accordingly, the DASH client controller can generate a command for acquiring necessary segments.

A segment parser can parse acquired segments in real time. Internal blocks such as the media engine can perform a specific operation according to information included in the segment.

An HTTP client can request a necessary MPD and/or segments from the HTTP server. In addition, the HTTP client can deliver the MPD and/or segments acquired from the server to the MPD parser or the segment parser.

The media engine can display content on the screen using media data included in segments. Here, information of the MPD can be used.

A DASH data model may have a hierarchical structure t50020. Media presentation can be described by the MPD. The MPD can describe a time sequence of a plurality of periods which forms media presentation. A period indicates one section of media content.

In one period, data can be included in adaptation sets. An adaptation set may be a set of media content components which can be exchanged. Adaption can include a set of representations. A representation can correspond to a media content component. In one representation, content can be temporally divided into a plurality of segments for appropriate accessibility and delivery. To access each segment, the URL of each segment may be provided.

The MPD can provide information related to media presentation and a period element, an adaptation set element and a representation element can describe a corresponding period, adaptation set and representation. A representation can be divided into sub-representations, and a sub-representation element can describe a corresponding sub-representation.

Here, common attribute/elements can be defined. The common attributes/elements can be applied to (included in) sub-representations. The common attributes/elements may include an essential property and/or a supplemental property.

The essential property may be information including elements regarded as mandatory elements in processing of corresponding media presentation related data. The supplemental property may be information including elements which may be used to process corresponding media presentation related data. In an embodiment, descriptors which will be described below may be defined in the essential property and/or the supplemental property and delivered through an MPD.

A DASH based descriptor may include an @schemeldUri field, an @value field and/or an @id field. The @schemeIdUri field can provide a URI through which the scheme of the corresponding descriptor is identified. The @value field can have values defined by the scheme indicated by the @ schemeldUri field. That is, the @ value field can have values of descriptor elements according to the scheme, which may be called parameters. The parameters can be discriminated by “,”. The @id can indicate the ID of the corresponding descriptor. When the descriptor has the same ID, the descriptor can include the same scheme ID, value and parameters.

The embodiments of 360 video related metadata may be rewritten as embodiments of a DASH based descriptor. When 360 video data is delivered according to DASH, 360 video related metadata may be described in the form of DASH descriptors, included in an MPD and delivered to a reception side. The descriptors may be delivered in the form of the aforementioned essential property descriptor and/or supplemental property descriptor. These descriptors may be included in the adaptation set, representation and sub-representation of the MPD and delivered.

The specification discloses methods of defining, storing and signaling related metadata in order to deliver information about a viewpoint (point) intended by a producer, such as a director's cut, such that a user can view the intended viewpoint (point) or region in reproduction of 360 video. Region information or viewpoint information which will be described below may be region information or viewpoint information indicating a region or a view (point) intended by a producer. The information about the recommended viewpoint (point) or region may refer to a region that is displayed on the user device when the user or the user device cannot control the direction or the viewpoint, or the direction control is released.

Information that needs to be delivered for the methods may correspond to a region in a 2D space, a viewpoint (point) in the 2D space, a region in a 3D space or a viewpoint (point) in the 3D space. The 2D space may refer to a captured or encoded rectangular image plane and the 3D space may refer to a projecting space or a projection structure for 360 video rendering, such as a spherical, cylindrical or square form. Here, the region may refer to the aforementioned region, and the region or viewpoint (point) in the 3D space may correspond to the region or viewpoint (point) in the 2D space. That is, the region or viewpoint (point) of the 2D space may be obtained by projecting/mapping the region or viewpoint (point) of the 3D space on a 2D frame.

<Method of Delivering Region and Viewpoint Information in 2D Space>

Region and viewpoint (point) information in a 2D space may be stored in a single track as timed metadata in ISOBMFF. Embodiments of metadata about region information in a 2D space and metadata about viewpoint (point) information in the 2D space will be sequentially described below.

FIG. 12 illustrates metadata about region information in a 2D space according to one embodiment of the present invention.

FIG. 12(a) illustrate a configuration of a sample entry of a track storing the region information in the 2D space and FIG. 12(b) illustrates a configuration of an individual sample for an individual region to be represented in the 2D space.

The sample entry of the track storing the region information in the 2D space may include reference_width, reference_height, min_top_left_x, max_top_left_x, min_top_left_y, max_top_left_y, min_width, max_width, min_height and/or max_height.

The reference_width indicates the horizontal size of the 2D space. Here, the horizontal size of the 2D space may be represented in number of pixels.

The reference_height indicates the vertical size of the 2D space. Here, the vertical size of the 2D space may be represented in number of pixels.

The min_top_left_x indicates a minimum value of the horizontal coordinate of the left top point of a region to be represented.

The max_top_left_x indicates a maximum value of the horizontal coordinate of the left top point of the region to be represented.

The min_top_left_y indicates a minimum value of the vertical coordinate of the left top point of the region to be represented.

The max_top_left_y indicates a maximum value of the vertical coordinate of the left top point of the region to be represented.

The min_width indicates a minimum value of the horizontal size of a region (region in the 2D space) to be represented. Here, the minimum value of the horizontal size of the region to be represented may be represented in number of pixels.

The max_width indicates a maximum value of the horizontal size of the region (region in the 2D space) to be represented. Here, the maximum value of the horizontal size of the region to be represented may be represented in number of pixels.

The min_height indicates a minimum value of the vertical size of a region (region in the 2D space) to be represented. Here, the minimum value of the vertical size of the region to be represented may be represented in number of pixels.

The max_height indicates a maximum value of the vertical size of a region (region in the 2D space) to be represented. Here, the maximum value of the vertical size of the region to be represented may be represented in number of pixels.

An individual sample for an individual region to be represented in the 2D space may include top_left_x, top_left_y, width, height and/or interpolate.

The top_left_x indicates the horizontal coordinate of the left top point of a region to be represented.

The top_left_y indicates the vertical coordinate of the left top point of the region to be represented.

The width indicates the horizontal size of the region to be represented. Here, the horizontal size of the region to be represented may be represented in number of pixels.

The height indicates the vertical size of the region to be represented. Here, the vertical size of the region to be represented may be represented in number of pixels.

The interpolate indicates whether values between a region represented by a previous sample and a region represented by a current sample are filled by linearly interpolated values. In an embodiment, when interpolate is 1, the values between the region represented by the previous sample and the region represented by the current sample can be filled by linearly interpolated values.

FIG. 13 illustrates metadata about a viewpoint (point) in a 2D space according to one embodiment of the present invention.

FIG. 13(a) illustrate a configuration of a sample entry of a track storing the viewpoint (point) information in the 2D space and FIG. 13(b) illustrates a configuration of an individual sample for an individual viewpoint (point) to be represented in the 2D space.

The sample entry of the track storing the point information in the 2D space may include reference_width, reference_height, min_x, max_x, min_y and/or max_y.

reference_width indicates the horizontal size of the 2D space. Here, the horizontal size of the 2D space may be represented in number of pixels.

reference_height indicates the vertical size of the 2D space. Here, the vertical size of the 2D space may be represented in number of pixels.

min_x indicates a minimum value of the horizontal coordinate of a point to be presented.

max_x indicates a maximum value of the horizontal coordinate of the point to be presented.

min_y indicates a minimum value of the vertical coordinate of the point to be presented.

max_y indicates a maximum value of the vertical coordinate of the point to be presented.

An individual sample for an individual point to be represented in the 2D space may include x, y and/or interpolate.

“x” indicates the horizontal coordinate of a point to be represented.

“y” indicates the vertical coordinate of the point to be represented.

“interpolate” indicates whether values between a region represented by a previous sample and a region represented by a current sample are filled by linearly interpolated values. In an embodiment, when interpolate is 1, the values between the region represented by the previous sample and the region represented by the current sample can be filled by linearly interpolated values.

<Method of Delivering Region and Viewpoint Information in 3D Space>

Region and viewpoint information in a 3D space may be stored in a single track as timed metadata in ISOBMFF. Embodiments of metadata about region information in a 3D space and metadata about viewpoint (point) information in the 3D space will be sequentially described below.

Here, the 3D space may refer to a sphere and 360-degree video may be represented on the sphere. The aforementioned 2D space may refer to a 3D plane onto which the 3D space is projected/mapped.

FIG. 14 illustrates metadata about region information in a 3D space according to various embodiments of the present invention.

FIG. 14(a) illustrate a configuration of a sample entry of a track storing the region information in the 3D space according to one embodiment of the present invention and FIG. 14(b) illustrates a configuration of a sample entry of a track storing the region information in the 3D space according to another embodiment of the present invention.

Referring to FIG. 14(a), the sample entry of the track storing the region information in the 3D space according to one embodiment of the present invention may include min_yaw, max_yaw, min_pitch, max_pitch, min_roll, max_roll, min_field_of_view and/or max_field_of_view.

min_yaw indicates a minimum value of a rotation amount with respect to the yaw axis of a region to be represented.

max_yaw indicates a maximum value of the rotation amount with respect to the yaw axis of the region to be represented.

min_pitch indicates a minimum value of a rotation amount with respect to the pitch axis of the region to be represented.

max_pitch indicates a maximum value of the rotation amount with respect to the pitch axis of the region to be represented.

min_roll indicates a minimum value of a rotation amount with respect to the roll axis of the region to be represented.

max_roll indicates a maximum value of the rotation amount with respect to the roll axis of the region to be represented.

min_field_of_view indicates a minimum value of field of view to be represented.

max_field_of_view indicates a maximum value of field of view to be represented.

When min_field_of_view and max_field_of_view are set to 0, a region of a sample which refers to the sample entry may be a point.

Referring to FIG. 14(b), the sample entry of the track storing the region information in the 3D space according to another embodiment of the present invention may include center_yaw, center_pitch, center_roll, horizontal_field_of_view and/or vertical_field_of_view.

center_yaw indicates a center value of a rotation amount with respect to the yaw axis of a region to be represented.

center_pitch indicates a center value of a rotation amount with respect to the pitch axis of the region to be represented.

center_roll indicates a center value of a rotation amount with respect to the roll axis of the region to be represented.

horizontal_field_of_view indicates a value of a horizontal field of view to be represented. This value may be a horizontal field of view based on center_yaw.

vertical_field_of_view indicates a value of a vertical field of view to be represented. This value may be a vertical field of view based on center_pitch.

When horizontal_field_of_view and vertical_field_of_view are set to 0, a region of a sample which refers to the sample entry may be a point.

horizontal_field_of_view and vertical_field_of_view of the corresponding sample entry may be applied to each sample as long as they are not changed in each sample.

In one embodiment, the sample entries of a track storing the region information in the 3D space according to one embodiment and/or another embodiment of the present invention may further include dynamic_range_flag. The dynamic_range_flag can indicate that horizontal and vertical fields of view indicated by a corresponding sample entry are not changed but are maintained for all samples which refer to the sample entry. For example, the dynamic_range_flag can indicate that horizontal and vertical fields of view of the sample entry are maintained in samples which refer to the sample entry when set to 0.

FIG. 15 illustrates metadata about an individual region to be represented in a 3D space according to various embodiments of the present invention.

FIG. 15(a) illustrates a configuration of an individual sample for an individual region to be represented in a 3D space according to one embodiment of the present invention and FIG. 15(b) illustrates a configuration of an individual sample for the individual region to be represented in the 3D space according to another embodiment of the present invention.

Referring to FIG. 15(a), the individual sample for the individual region to be represented in the 3D space according to one embodiment of the present invention may include yaw, pitch, roll, field_of_view and/or interpolate.

“yaw” indicates a rotation amount with respect to the yaw axis of the region to be represented.

“pitch” indicates a rotation amount with respect to the pitch axis of the region to be represented.

“roll” indicates a rotation amount with respect to the roll axis of the region to be represented.

In an embodiment, “yaw” and “pitch” may indicate the center of a viewport and the roll may indicate a roll angle of the viewport.

field_of_view indicates a field of view to be represented. The field of view may be subdivided into horizontal_field_of_view and vertical_field_of_view.

horizontal_field_of_view indicates a value of a horizontal field of view to be represented. This value may be a horizontal field of view based on center_yaw.

vertical_field_of_view indicates a value of a vertical field of view to be represented. This value may be a vertical field of view based on center_pitch.

“interpolate” indicates whether values between a region represented by a previous sample and a region represented by a current sample are filled by linearly interpolated values. In an embodiment, when interpolate is 1, the values between the region represented by the previous sample and the region represented by the current sample can be filled by linearly interpolated values.

Referring to FIG. 15(b), the individual sample for the individual region to be represented in the 3D space according to another embodiment of the present invention may include yaw, pitch, roll and/or interpolate.

“yaw” indicates a rotation amount with respect to the yaw axis of the region to be represented.

“pitch” indicates a rotation amount with respect to the pitch axis of the region to be represented.

“roll” indicates a rotation amount with respect to the roll axis of the region to be represented.

“interpolate” indicates whether values between a region represented by a previous sample and a region represented by a current sample are filled by linearly interpolated values. In an embodiment, when interpolate is 1, the values between the region represented by the previous sample and the region represented by the current sample can be filled by linearly interpolated values.

FIG. 16 illustrates metadata about region information in a 3D space according to another embodiment of the present invention.

FIG. 16(a) shows configuration of a sample entry of a track for storing region information in a 3D space according to another embodiment of the present invention, and FIG. 16(b) shows configuration of individual samples for individual regions to be rendered in a 3D space.

Referring to FIG. 16(a), a sample entry of a track for storing region information in a 3D space according to another embodiment of the present invention may include region_type, reference_yaw_center, reference_pitch_center, reference_roll_center, reference_width, reference_height and/or reference_roll_range.

region_type may identify the type of a region to be rendered.

For example, if region_type is 0, the corresponding region may be a viewport in a user device such as a head-mounted display (HMD). Here, the viewport may be generated in the same way as in rectilinear projection. In this case, the region may be an inner region composed of an intersection of two horizontal great circles present on a spherical surface and two horizontal great circles. In other words, the region may be a region on the spherical surface specified by four great circles.

For example, if region_type is 1, the corresponding region may be a viewpoint set, which is a set of viewpoints, that may be represented by a specific range of yaw, pitch, and roll that should be included in the viewport of the user device. In this case, the region may be a region composed of an intersection of two horizontal great circles and two horizontal small circles present on the spherical surface. In a more specific embodiment, the region may be a spherical region defined by two pitch circles and two yaw circles present on the spherical surface.

Meanwhile, when region_type is set to 1, the viewport in the user device may be configured according to the value of the unique horizontal/vertical field of view of the user device, and the viewpoint set region may be included in the viewport.

In an embodiment, if the region_type field is not included in the metadata, the region identification method may be set to one of the region identification methods denoted by region_type. In other words, if the region_type field is not included in the metadata, the region identification method may be preset to a case where region_type is 0, or may be preset to a case where region_type is 1, in which the region_type field may not be signaled.

reference_yaw_center may indicate the yaw value of the center point of the reference space that defines a region where samples present in the track may be presented. Here, the samples may be defined by 3DSphericalCoordinatesSample( ), which will be described later.

reference_pitch_center may indicate the pitch value of the center point of the reference space that defines a region where samples present in the track may be presented. Here, the samples may be defined by 3DSphericalCoordinatesSample( ), which will be described later.

reference_roll_center may indicate the roll value of the center point of the reference space that defines a region where samples present in the track may be presented. Here, the samples may be defined by 3DSphericalCoordinatesSample( ), which will be described later.

reference_width may indicate the horizontal width of the reference space that defines a region where samples present in the track may be presented. Here, the samples may be defined by 3DSphericalCoordinatesSample( ), which will be described later.

The meaning of reference_width may depend on the value of region_type.

In one example, when reference_type is 0, reference_width may indicate the horizontal field of view of a viewport in a user device such as a head-mounted display (HMD). Here, the viewport may be generated in the same way as in rectilinear projection.

In another example, when reference_type is 1, reference_width may indicate the range of yaw values of the points constituting a reference space for a viewpoint set.

Reference_height may indicate a vertical height of a reference space defining a region in which samples present in the track may be presented. Here, the samples may be defined by 3DSphericalCoordinatesSample( ), which will be described later.

The meaning of reference_height may depend on the value of region_type.

In one example, when reference_type is 0, reference_height may indicate the vertical field of view of a viewport in a user device such as a head-mounted display (HMD). Here, the viewport may be generated in the same way as in rectilinear projection.

In another example, when reference_type is 1, reference_height may indicate a range of pitch values of the points constituting a reference space for a viewpoint set.

reference_roll_range may indicate the range of roll values of the reference space with respect to the center point.

Next, referring to FIG. 16(b), an individual sample for an individual region to be rendered in a 3D space according to another embodiment of the present invention may include yaw_center, pitch_center, roll_center, width, height and/or interpolate.

yaw_center may indicate the yaw value of the center point of the region to be rendered.

pitch_center may indicate the pitch value of the center point of the region to be rendered.

roll_center may indicate the roll value of the center point of the region to be rendered.

“width” may indicate the horizontal width of the region to be rendered. The width may depend on the value of region_type described above.

In one example, when reference_type is 0, “width” may indicate the horizontal field of view of a viewport in a user device such as a head-mounted display (HMD). Here, the viewport may be generated in the same way as in rectilinear projection.

In another example, when reference_type is 1, “width” may indicate a range of yaw values of the points constituting a reference space for a viewpoint set.

“height” may indicate the vertical height of a region to be rendered. The meaning of “height” may depend on the value of region_type described above.

In one example, when reference_type is 0, “height” may indicate the vertical field of view of a viewport in a user device such as a head-mounted display (HMD). Here, the viewport may be generated in the same way as in rectilinear projection.

In another example, when reference_type is 1, “height” may indicate a range of pitch values of the points constituting a reference space for a viewpoint set.

“interpolate” may indicate whether to use linearly interpolated values as the values between the region represented by the previous sample and the region represented by the current sample. In an embodiment, when interpolate is 1, the values between the region represented by the previous sample and the region represented by the current sample may be represented by linearly interpolated values.

FIG. 17 illustrates metadata about region information in a 3D space according to another embodiment of the present invention.

FIG. 17(a) shows configuration of a sample entry of a track for storing region information in a 3D space according to another embodiment of the present invention, and FIG. 17(b) shows configuration of individual samples for individual regions to be rendered in a 3D space.

The embodiment of FIG. 17 differs from the embodiment of FIG. 16 in that different fields may be configured depending on the value of region_type.

Referring to FIG. 17 (a), a sample entry of a track for storing region information in a 3D space according to another embodiment of the present invention may include region_type, reference_yaw_center, reference_pitch_center, reference_roll_center, reference_horizontal_field_of_view, reference_vertical_field_of_view, reference_viewpoint_yaw_range, reference_viewpoint_pitch_range and/or reference_roll_range.

For region_type, reference_yaw_center, reference_pitch_center, reference_roll_center and reference_roll_range, the description of FIG. 16(a) may be applied.

In this embodiment, when the region_type is 0, reference_horizontal_field_of_view and reference_vertical_field_of_view may be included in the sample entry.

reference_horizontal_field_of_view may indicate the horizontal field of view of a viewport corresponding to a reference space in a user device such as a head-mounted display (HMD). Here, the viewport may be generated in the same way as in rectilinear projection.

reference_vertical_field_of_view may indicate the vertical field of view of a viewport corresponding to the reference space in a user device such as a head-mounted display (HMD). Here, the viewport may be generated in the same way as in rectilinear projection.

In this embodiment, when region_type is 1, reference_viewpoint_yaw_range and reference_viewpoint_pitch_range may be included in the sample entry.

reference_viewpoint_yaw_range may indicate the range of yaw values of the points constituting a reference space for a viewpoint set.

reference_viewpoint_pitch_range may indicate the range of pitch values of the points constituting the reference space for the viewpoint set.

Next, with reference to FIG. 17(b), an individual sample for an individual region to be rendered in a 3D space according to another embodiment of the present invention may include yaw_center, pitch_center, roll_center, horizontal_field_of_view, vertical_field_of_view, viewpoint_yaw_range, viewpoint_pitch_range and/or interpolate.

For yaw_center, pitch_center, roll_center, and interpolate, the description given of FIG. 16(b) may be applied.

In this embodiment, when region_type is 0, horizontal_field_of_view and vertical_field_of_view may be included in the corresponding samples.

horizontal_field_of_view may indicate the horizontal field of view of a viewport corresponding to a region in a user device such as a head-mounted display (HMD). Here, the viewport may be generated in the same way as in rectilinear projection.

vertical_field_of_view may indicate the vertical field of view of a viewport corresponding to a region in a user device such as a head-mounted display (HMD). Here, the viewport may be generated in the same way as in rectilinear projection.

In this embodiment, when the region_type is 1, viewpoint_yaw_range and viewpoint_pitch_range may be included in the corresponding sample.

viewpoint_yaw_range may indicate the range of yaw values of the points constituting a viewpoint set.

viewpoint_pitch_range may indicate the range of pitch values of the points constituting the viewpoint set.

FIG. 18 illustrates metadata about region information in a 3D space according to another embodiment of the present invention.

FIG. 18(a) shows configuration of a sample entry of a track for storing region information in a 3D space according to another embodiment of the present invention, and FIG. 18(b) shows configuration of individual samples for individual regions to be rendered in a 3D space.

In the embodiment of FIG. 18, the sample entry may be composed of different fields depending on the value of region_type, and the individual sample is configured to include both a field to be included when region_type is 0 and a field to be included when region_type is 1.

Referring to FIG. 18(a), a sample entry of a track for storing region information in a 3D space according to another embodiment of the present invention may include reference_yaw_center, reference_pitch_center, reference_roll_center, reference_horizontal_field_of_view, reference_vertical_field_of_view, reference_viewpoint_yaw_range, reference_viewpoint_pitch_range and/or reference_roll_range.

Next, referring to FIG. 18(b), an individual sample for an individual region to be rendered in a 3D space according to another embodiment of the present invention may include yaw_center, pitch_center, roll_center, horizontal_field_of_view, vertical_field_of_view, viewpoint_yaw_range, viewpoint_pitch_range and/or interpolate.

When the embodiment illustrated in FIG. 18 is compared with the embodiment of FIG. 17, the embodiment of FIG. 18(b) is distinguished in that both a field to be included when region_type is 0 and a field to be included when region_type is 1 are included in the sample at the same time.

In the embodiment of FIG. 18 (FIG. 18(a)), the reference space of a region to be rendered may be a superset of viewpoints for any points belonging to the range of reference_viewpoint_yaw_range and reference_viewpoint_pitch_range and a viewport determined by the values of reference_horizontal_field_of_view and reference_vertical_field_of_view.

In the embodiment of FIG. 18 (FIG. 18(b)), a region to be rendered may be a superset of viewpoints for any points belonging to the range of viewpoint_yaw_range and viewpoint_pitch_range and a viewport determined by the values of horizontal_field_of_view and vertical_field_of_view.

In the embodiments of FIGS. 17 and 18, fields assigned the same names are substantially the same, and therefore, the corresponding description of FIG. 17 may be applied to each field of FIG. 18

FIG. 19 is a reference diagram illustrating a method of defining a region by a region type according to an embodiment of the present invention.

FIG. 19(a) shows a spherical 3D model, FIG. 19(b) shows a region composed of an intersection of two great circles and two great circles, and FIG. 19(c) shows a region composed of an intersection of two great circles and two small circles.

First, the meanings of a great circle, a small circle, a pitch circle, and a yaw circle will be described.

A great circle may refer to a circle that passes through the center of a sphere. More specifically, a great circle may refer to points of intersection between a plane passing through the center point of a sphere and the sphere. The great circle may be referred to as an orthodrome or a Riemannian circle. On the other hand, the center of the sphere and the center of the great circle may be the same position.

A small circle may refer to a circle that does not pass through the center of the sphere.

A pitch circle may refer to a circle on a sphere surface connecting all points having the same pitch value. The pitch circle, like the latitude on Earth, may not be a great circle.

A yaw circle may refer to a circle on the sphere surface connecting all points having the same yaw value. The yaw circle is always a great circle, just like the longitude on Earth.

As described above, “region type” according to an embodiment of the present invention may indicate a type specifying a region present on the spherical surface.

FIG. 19(b) illustrates specifying a region on a spherical surface when “region type” according to an embodiment of the present invention is 0.

Since “region type” is 0, the region on the spherical surface is specified by four great circles. More specifically, the region on the spherical surface is specified by two pitch circles and two yaw circles.

As shown in the figure, the center of the specified region on the spherical surface may be represented by center_pitch, center_yaw. center_pitch and center_yaw may be used to define a viewport together with field-of-view information such as a horizontal field of view (or width) and a vertical field of view (or height).

In other words, if region_type is 0, the region may be an inner curved surface whose boundary is defined by two vertical great circles having yaw values of center_yaw−horizontal_field_of_view/2 and center_yaw+horizontal_field_of_view/2 and two horizontal great circles having pitch values of center_pitch−vertical_field_of_view/2 and center_pitch+vertical_field_of_view/2.

FIG. 19(c) illustrates specifying a region on a spherical surface when “region type” according to an embodiment of the present invention is 1.

Since the region type is 1, the region on the spherical surface is specified by two great circles and two small circles. More specifically, the region on the spherical surface is specified by two pitch circles and two yaw circles. Here, the two pitch circles are small circles, not great circles.

As shown in the figure, the center of the specified region on the spherical surface may be represented by center_pitch and center_yaw. center_pitch and center_yaw may be used to define a viewport together with field-of-view information such as a horizontal field of view and a vertical field of view.

In other words, if region_type is 0, the region may be an inner curved surface whose boundary is defined by two vertical great circles having yaw values of center_yaw−horizontal_field_of_view/2 and center_yaw+horizontal_field_of_view/2, and two horizontal small circles having pitch values of center_pitch−vertical_field_of_view/2 and center_pitch+vertical_field_of_view/2.

<Method of Signaling Relationship Between Metadata Track with Respect to Region Information or Viewpoint Information and 360-Degree Video Track>

A metadata track regarding region information or viewpoint information and a 360-degree video track to which such metadata will be applied may be signaled through the following method.

First, a method of signaling a relationship between 360-degree video tracks will be described.

In an embodiment, when one video frame is divided into one or more regions, the regions are coded and data about the regions are delivered through one or more tracks, 360-degree video related metadata about each track may be included in the form of box. Here, the 360-degree video related metadata may be the 360-degree video related metadata described above with reference to FIGS. 2, 3, 4 and 8. When the 360-degree video related metadata is included in the form of box, the 360-degree video related metadata may be defined as OMVideoConfigurationBox class. OMVideoConfigurationBox may be called an omvb box. The 360-degree video related metadata may be included in various levels such as a file, a fragment, a track, a sample entry and a sample and delivered and may provide metadata about data of the level corresponding thereto (track, stream, sample, etc.).

When only some specific tracks include OMVideoConfigurationBox and the remaining tracks do not include OMVideoConfigurationBox, signaling through which the remaining tracks can refer to the tracks including OMVideoConfigurationBox is needed. To this end, information indicating the tracks including OMVideoConfigurationBox may be included in TrackReferenceTypeBox of the remaining tracks which do not include OMVideoConfigurationBox. According to an embodiment, a track reference type of “omvb” may be defined and tracks including 360-degree video related metadata may be indicated through track IDs included in the corresponding TrackReferenceTypeBox.

Next, a method of signaling a relationship between a metadata track regarding region information or viewpoint information and a 360-degree video track will be described.

The metadata track regarding region information or viewpoint information may be stored and delivered separately from the 360-degree video track. In other words, metadata about region information or viewpoint information may be delivered through a track separated from the 360-degree video track. When the metadata about region information or viewpoint information is included in a track and delivered in this manner, referencing between the track including the metadata about region information or viewpoint information and the 360-degree video track related to the metadata track may be required.

According to an embodiment, referencing between the metadata track about region information or viewpoint information and the 360-degree video track related to the metadata track may be performed using “cdsc” reference type defined in TrackReferenceBox(‘tref’) which is one of boxes of the ISOBMFF.

According to another embodiment, referencing between the metadata track about region information or viewpoint information and the 360-degree video track related to the metadata track may be performed by newly defining a reference type of “vdsc” in TrackReferenceBox(‘tref’)

FIG. 20 illustrates a tref box according to an embodiment of the present invention.

The TrackReference(‘tref’) box provides a reference between tracks included therein and other tracks. The TrackReference(‘tref’) box may include a predetermined reference type and one or more track reference type boxes having IDs.

Track_ID may be an integer which provides a reference for other tracks in presentation in the track corresponding thereto. The track_ID is not reused and cannot be 0.

Reference_type may be set to one of the following values. Further, the reference_type may be set to values which are not defined in the following.

A track referred to by “hint” may include original media of the corresponding hint track.

A “cdsc” track describes a referenced track. This track may include timed metadata about a reference track.

A “font” track may use a font delivered/defined in a referenced track.

A “hind” track depends on a referenced hint track. That is, this track can be used when the referenced hint track is used.

A “vdep” track may include auxiliary depth video information about a referenced video track.

A “vplx” track may include auxiliary parallax video information about a referenced video track.

A “subt” track may include subtitle, timed text and/or overlay graphic information about a referenced track or all tracks of a substitute group including the corresponding track.

A “vdsc” track may be a reference type which correlates a metadata track delivering region information with a 360 video track. In one embodiment, a track including the tref box having this reference_type may be a metadata track which delivers region information or viewpoint information. Here, track_IDs included in the tref box can reference the 360 video track. In another embodiment, a track including the tref box having this reference_type may be a 360 video track. Here, track_IDs included in the tref box can reference a metadata track which delivers region information or viewpoint information.

In addition, a reference type of “cdsc” may be used in order to reference a metadata track about region information or viewpoint information and a 360-degree video track related to the metadata track.

That is, to reference the metadata track about region information or viewpoint information and the 360-degree video track related to the metadata track, the reference type of “cdsc” or “vdsc” may be used.

<GPS Information Delivery Method>

GPS information may be stored in a single track as timed metadata in the ISOBMFF. A description will be given of embodiments of metadata about GPS information.

FIG. 21 illustrates metadata about GPS according to an embodiment of the present invention.

FIG. 21(a) illustrates a configuration of a sample entry of a track which stores GPS information according to an embodiment of the present invention, FIG. 21(b) illustrates a configuration of an individual sample which stores GPS data according to an embodiment of the present invention and FIG. 21(c) illustrates a configuration of an individual sample which stores GPS data according to another embodiment of the present invention.

The sample entry of the track which stores the GPS information may include coordinate_reference_sys and/or altitude_flag.

The coordinate_reference_sys indicates a coordinate reference system (CRS) with respect to latitude, longitude and altitude values included in the sample. The coordinate_reference_sys may be represented as a URI (Uniform Resource Identifier). For example, the coordinate_reference_sys can indicate “urn:ogc:def:crs:EPSG::4979”. Here, “urn:ogc:def:crs:EPSG::4979” can indicate a coordinate reference system (CRS) having code 4979 in an EPSG database.

The altitude_flag indicates whether the sample includes an altitude value. In one embodiment, the altitude_flag may indicate that the sample includes an altitude value when set to 1 and indicate that the sample does not include an altitude value when set to 0.

GPS data may be stored in an individual sample. Embodiments with respect to a configuration of GPS data which can be stored in an individual sample are shown in FIGS. 21(b) and 21(c).

FIG. 21(b) illustrates a configuration of an individual sample which stores GPS data according to an embodiment of the present invention. A GPS data sample shown in FIG. 21(b) may include longitude, latitude and/or altitude.

The longitude indicates a longitude value of a point. A positive value may indicate an eastern longitude and a negative value may indicate a western longitude.

The latitude indicates a latitude value of the point. A positive value may indicate a northern latitude and a negative value may indicate a southern latitude.

The altitude indicates an altitude value of the point. In one embodiment, when the altitude flag of a sample entry indicates that the sample includes an altitude value (ex. altitude flag=1), the sample may include an altitude. In another embodiment, when the altitude flag of the sample entry indicates that the sample does not include an altitude value (ex. altitude flag=0), the sample may not include an altitude. An embodiment in which a sample does not include an altitude is described with reference to FIG. 21(c).

FIG. 21(c) illustrates a configuration of an individual sample which stores GPS data according to another embodiment of the present invention. A GPS data sample illustrated in FIG. 21(c) may include longitude and/or latitude. The GPS data sample illustrated in FIG. 21(c) may not include altitude.

The longitude indicates a longitude value of a point. A positive value may indicate an eastern longitude and a negative value may indicate a western longitude.

The latitude indicates a latitude value of the point. A positive value may indicate a northern latitude and a negative value may indicate a southern latitude.

<Method of Signaling Relationship Between GPS Information Delivery Metadata Track and 360-Degree Video Track>

A metadata track regarding GPS information and a 360-degree video track to which such metadata will be applied may be signaled through the following method.

First, a method of signaling a relationship between 360-degree video tracks will be described.

In one embodiment, when one video frame is divided into one or more regions, the regions are coded and data about the regions are delivered through one or more tracks, 360-degree video related metadata about each track may be included in the form of box. Here, the 360-degree video related metadata may be the 360-degree video related metadata describe above with reference to FIGS. 2, 3, 4 and 8. When the 360-degree video related metadata is included in the form of box, the 360-degree video related metadata may be defined as OMVideoConfigurationBox class. OMVideoConfigurationBox may be called an omvb box. The 360-degree video related metadata may be included in various levels such as a file, a fragment, a track, a sample entry and a sample and delivered and may provide metadata about data of the level corresponding thereto (track, stream, sample, etc.).

When only some specific tracks include OMVideoConfigurationBox and the remaining tracks do not include OMVideoConfigurationBox, signaling through which the remaining tracks can refer to the tracks including OMVideoConfigurationBox is needed. To this end, information indicating the tracks including OMVideoConfigurationBox may be included in TrackReferenceTypeBox of the remaining tracks which do not include OMVideoConfigurationBox. According to an embodiment, a track reference type of “omvb” may be defined and tracks including 360-degree video related metadata may be indicated through track IDs included in the corresponding TrackReferenceTypeBox.

Next, a method of signaling a relationship between a metadata track regarding GPS information and a 360-degree video track will be described.

The metadata track regarding GPS information may be stored and delivered separately from the 360-degree video track. In other words, metadata about GPS information may be delivered through a track separated from the 360-degree video track. When the metadata about GPS information is included in a track and delivered in this manner, referencing between the track including the metadata about GPS information and the 360-degree video track related to the metadata track may be required.

According to an embodiment, referencing between the metadata track about GPS information and the 360-degree video track related to the metadata track may be performed using “cdsc” reference type defined in TrackReferenceBox(‘tref’) which is one of boxes of the ISOBMFF.

According to another embodiment, referencing between the metadata track about GPS information and the 360-degree video track related to the metadata track may be performed by newly defining a reference type of “gpsd” in TrackReferenceBox(‘tref’).

Referring back to FIG. 20, FIG. 20 illustrates a tref box according to an embodiment of the present invention.

The TrackReference(‘tref’) box provides reference between tracks included therein and other tracks. The TrackReference(‘tref’) box may include a predetermined reference type and one or more track reference type boxes having IDs. Here, “gpsd” may be newly defined and used as a reference type.

A track_ID may be an integer which provides reference for other tracks in presentation in the track corresponding thereto. The track_ID is not reused and cannot be 0.

A reference_type may be set to one of the following values. Further, the reference_type may be set to values which are not defined in the following.

A track referred to by “hint” may include original media of the corresponding hint track.

A “cdsc” track describes a referred track. This track may include timed metadata about a reference track.

A “font” track may use a font delivered/defined in a referred track.

A “hind” track depends on a referenced hint track. That is, this track can be used when the referenced hint track is used.

A “vdep” track may include auxiliary depth video information about a referenced video track.

A “vplx” track may include auxiliary parallax video information about a referenced video track.

A “subt” track may include subtitles, timed text and/or overlay graphic information about a referenced track or all tracks of a substitute group including the corresponding track.

A “gpsd” track may be a reference type which correlates a metadata track delivering GPS information with a 360 video track. In one embodiment, a track including the tref box having this reference_type may be a metadata track which delivers GPS information. Here, track_IDs included in the tref box can reference the 360 video track. In another embodiment, a track including the tref box having this reference_type may be a 360 video track. Here, track_IDs included in the tref box can reference a metadata track which delivers GPS information.

In addition, a reference type of “cdsc” may be used in order to reference a metadata track about GPS information and a 360-degree video track related to the metadata track.

That is, to reference the metadata track about GPS information and the 360-degree video track related to the metadata track, the reference type of “cdsc” or “vdsc” may be used.

The methods disclosed in the specification can be applied to a case in which a file with respect to content supporting 360 video services is generated on the basis of a box based file format such as ISOBMFF, a DASH segment which can operate in MPEG DASH is generated or an MPU which can operate in an MPEG MMT is generated. In addition, a receiver including a DASH client or an MMT client may effectively decode and display the content on the basis of 360 video related metadata (flags, parameters, etc.).

The aforementioned sample entries and/or samples (e.g., 2DReagionCartesianCoordinatesSampleEntry, 2DPointCartesianCoordinatesSampleEntry, 3DCartesianCoordinatesSampleEntry, and GPSSampleEntry) for metadata about region information or viewpoint information and/or metadata about GPS information may be simultaneously present in a single ISOBMFF filed, a DASH segment or multiple boxes in an MMT MPU.

In this case, values of 360 video related flags or 360 video metadata defined in a lower box may override values of metadata about region information or viewpoint information and/or GPS information defined in an upper box.

A description will be given of embodiments related to methods of transmitting and signaling metadata about region information or viewpoint information, described above with reference to FIGS. 12 to 20, on the basis of DASH.

<Methods of Transmitting and Signaling Metadata about Region Information or Viewpoint Information Using DASH>

Embodiment of Configuring Additional Adaptation Set for Metadata Transmission

When metadata about region information or viewpoint information is transmitted through DASH, an additional adaptation set for metadata transmission may be configured. In this case, signaling for indicating transmission of the metadata about region information or viewpoint information through the additional adaptation set needs to be included in an MPD. In an embodiment, a role descriptor may be used as signaling for indicating transmission of the metadata about region information or viewpoint information through the additional adaptation set.

A new schemeldUri value may be allocated to discriminate a role scheme from the conventional role scheme in the MPD. For example, a new schemeldUri value such as “urn:mpeg:dash:role:201X” can be allocated for the role scheme. “dirc” may be allocated to such a new scheme as a value for indicating the metadata about region information or viewpoint information. Here, “dirc” allocated as a value for indicating the metadata about region information or viewpoint information is exemplary and values other than “dirc” may be allocated. In the case of an adaptation set for transmission of VR video or 360 video, “main” may be allocated to the value.

To signal a relationship between a representation for VR video transmission and a representation for transmission of metadata about region information or viewpoint information, Representation@associationId and associationType may be used. The representation for transmission of metadata about region information or viewpoint information may indicate id (“VR_video”) of the representation for transmission of VR video to which the metadata will be applied using associationId, and “dirc” may be allocated as associationType therein. Here, “dirc” may be newly defined as a value indicating the metadata about region information or viewpoint information. This method may be used to represent a relationship between tracks of the ISO BMFF (ISO Base Media File Format) in addition to DASH. That is, track_IDs of the “tref” box may be used instead of associationId and reference_type of the “tref” box may be used instead of associationType for the same purpose.

FIG. 22 illustrates an MPD which signals transmission of metadata about region information or viewpoint information according to an embodiment of the present invention.

Referring to FIG. 22, the MPD includes signaling for indicating transmission of metadata about region information or viewpoint information through an additional adaptation set.

In addition, in the embodiment illustrated in FIG. 22, a role descriptor is used as signaling for indicating transmission of metadata about region information or viewpoint information through an additional adaptation set.

In the embodiment illustrated in FIG. 22, “urn:mpeg:dash:role:201X” is allocated to the role scheme and “dirc” is allocated to the value in order to indicate transmission of the metadata about region information or viewpoint information through the additional adaptation set (H22020). In the case of an adaptation set for VR video transmission, “urn:mpeg:dash:role:2011” is allocated to the role scheme and “main” is allocated to the value (H22010).

Furthermore, in the embodiment illustrated in FIG. 22, Representation@ associationId and associationType are used in order to signal a relationship between a representation for VR video transmission and a representation for transmission of the metadata about region information or viewpoint information. The representation (representation id=“directors_cut”) for transmission of the metadata about region information or viewpoint information indicates id (“VR_video”) of the representation for transmission of VR video to which the metadata will be applied using associationId, and “dirc” is allocated as associationType therein (H22030).

As in the embodiment of FIG. 22, a new role scheme may be defined in order to signal transmission of metadata about region information or viewpoint information. Alternatively, a method compatible with the conventional role scheme may be used in order to signal transmission of metadata about region information or viewpoint information.

FIG. 23 illustrates an MPD which signals transmission of metadata about region information or viewpoint information according to another embodiment of the present invention.

Referring to FIG. 23, the MPD includes signaling for indicating transmission of metadata about region information or viewpoint information through an additional adaptation set.

Referring to FIG. 23, “urn:mpeg:dash:role:2011” is allocated to the role scheme and “metadata” is allocated to the value (H23020). In the case of an adaptation set for VR video transmission, “urn:mpeg:dash:role:2011” is allocated to the role scheme and “main” is allocated to the value (H23010). That is, the embodiment of FIG. 23 may be regarded as an embodiment in which the conventional adaptation set identification method (Role@ schemeIdUri=“urn:mpeg:dash:role:2011”, value=“metadata”) for metadata transmission is applied to identification of an adaptation set for transmission of metadata about region information or viewpoint information.

In addition, in the embodiment illustrated in FIG. 23, Representation@ associationId and associationType are used in order to signal a relationship between a representation for VR video transmission and a representation for transmission of the metadata about region information or viewpoint information. The representation (representation id=“directors_cut”) for transmission of the metadata about region information or viewpoint information indicates id (“VR_video”) of the representation for transmission of VR video to which the metadata will be applied using associationId, and “dirc” is allocated as associationType therein (H23030).

A description will be given of receiver operation related to the methods of transmitting and signaling metadata about region information or viewpoint information through an additional adaptation set, described above with reference to FIGS. 18 and 19.

FIG. 24 is a block diagram of a receiver according to an embodiment of the present invention.

Referring to FIG. 24, the receiver according to an embodiment of the present invention may include a DASH client H24020, segment parsers H24030, a video decoder H24040, a DIRC parser H24050 and/or a projector/renderer/sensors H24060.

An MPD, VR content and/or metadata about region information or viewpoint information may be provided by a DASH server H24010 and received by the DASH client H24020. Here, the DASH client H24020 of the receiver may receive VR content, MPD and/or metadata about region information or viewpoint information in a data packet format from the DASH server H24010. The DASH client H24020 may request the MPD, VR content and/or metadata about region information or viewpoint information from the DASH server H24010. The DASH client H24020 may generate an MPD and a segment from a received packet.

The DASH client H24020 may parse the received MPD to acquire information about content (VR content). Here, the DASH client H24020 may recognize presence or absence of the metadata about region information or viewpoint information through signaling with respect to an adaptation set through which the metadata about region information or viewpoint information is transmitted, described above with reference to FIGS. 22 and 23. In addition, the DASH client H24020 may activate the DIRC parser and the segment parser for DIRC depending on capabilities of the receiver and/or purpose of use of the content (refer to the dotted line of the figure). For example, when the receiver cannot process the metadata about region information or viewpoint information or does not use the metadata about region information or viewpoint information according to purpose, the adaptation set through which the metadata about region information or viewpoint information is transmitted may not be used (may be skipped). The segment may be delivered to the segment parser H24030.

The segment parser H24030 may parse the received segment and respectively deliver a video bitstream and metadata (DIRC metadata) about region information or viewpoint information to the video decoder H24040 and the DIRC parser H24050. The segment parser H24030 may be functionally classified according to parsing target. That is, the segment parser H24030 may be classified into a segment parser for parsing a segment for video and a segment parser for metadata about region information or viewpoint information.

The video decoder H24040 may decode the video bitstream and deliver the decoded video bitstream to the projector/renderer/sensors H24060.

The DIRC parser H24050 may parse the DIRC metadata and deliver the parsed information (DIRC info) to the projector/renderer/sensors H24060.

The projector/renderer/sensors H24060 may receive the video bitstream from the video decoder H24040 and receive the DIRC metadata from the DIRC parser H24050. In addition, the projector/renderer/sensors H24060 may provide video data to a user using the DIRC information. A method through which the projector/renderer/sensors H24060 provide VR content to the user using the DIRC information may depend on application. For example, a viewpoint intended by a producer and indicated by DIRC can be displayed to the user through auto navigation. As another example, VR content can be displayed depending on the viewpoint of the user with direction indication for guiding the viewpoint intended by the producer.

FIG. 25 illustrates an MPD which signals transmission of metadata about region information or viewpoint information according to another embodiment of the present invention.

In the embodiment illustrated in FIG. 25, VR video is composed of two or more spatial regions and is transmitted through two or more adaptation sets, distinguished from the embodiments of FIGS. 22 and 23. In the example of FIG. 25, the VR video is divided into a left spatial region and a right spatial region which respectively correspond to VR video tiles. The two VR video tiles correspond to two adaptation sets. A spatial relationship between the two VR video tiles is described through SRD (SupplementalProperty@ schemeIdUri=“urn:mpeg:dash:srd:2014”). More specifically, spatial information of the VR video tile corresponding to the left spatial region is described through <SupplementalProperty schemeIdUri=“urn:mpeg:dash:srd:2014” value=“1, 0, 0, 1920, 1920, 3840, 1920, 0”/> (H25010) and spatial information of the VR video tile corresponding to the right spatial region is described through <supplementalProperty schemeIdUri=“urn:mpeg:dash:srd:2014” value=“1, 0, 1920, 1920, 1920, 3840, 1920, 0”/> (H25020).

In addition, the metadata about region information or viewpoint information may be identified through Role@value=“dirc” or “metadata” as in the embodiments of FIGS. 22 and 23. In the present embodiment, a new role scheme is defined and Role@value=“dirc” is allocated to identify the metadata about region information or viewpoint information is used as in the embodiment of FIG. 22 (H25030).

Representation@ associationId may indicate representations of VR video tiles corresponding to two or more spatial regions or a single representation (representation for transmission of a base tile track). The present embodiment indicates VR video tile 1 and VR video type 2 corresponding to two spatial regions (H25040).

A description will be given of receiver operation related to the method of transmitting and signaling metadata about region information or viewpoint information in the embodiment in which VR video is divided into two or more spatial regions and transmitted through two or more adaptation sets, described with reference to FIG. 25.

FIG. 26 is a block diagram of a receiver according to another embodiment of the present invention.

Referring to FIG. 26, the receiver according to another embodiment of the present invention may include a DASH client H26020, segment parsers H26030, a video decoder H26040, a DIRC parser H26050 and/or a projector/renderer/sensors H26060.

An MPD, VR content and/or metadata about region information or viewpoint information may be provided by a DASH server H26010 and received by the DASH client H26020. Here, the DASH client H26020 of the receiver may receive VR content, MPD and/or metadata about region information or viewpoint information in a data packet format from the DASH server H26010. The DASH client H26020 may request the MPD, VR content and/or metadata about region information or viewpoint information from the DASH server H26010. The DASH client H26020 may generate an MPD and a segment from a received packet.

In the embodiment of FIG. 22, the data packet transmitted from the DASH sever H26010 may be part of spatial regions (e.g., VR video tile) of VR video. That is, VR video content transmitted from the DASH server H26010 may correspond to a spatial region (tile) including the initial viewpoint of the user or a spatial region (tile) including a viewpoint or region intended by a producer, which is indicated by information (DIRC info) delivered from the DIRC parser H26050 which will be described below.

The DASH client H26020 may parse the received MPD to acquire information about content (VR content). Here, the DASH client H26020 may recognize presence or absence of the metadata about region information or viewpoint information through signaling with respect to an adaptation set through which the metadata about region information or viewpoint information is transmitted, described above with reference to FIG. 24. In addition, the DASH client H26020 may activate the DIRC parser and the segment parser for DIRC depending on capabilities of the receiver and/or purpose of use of the content (refer to the dotted line of the figure). For example, when the receiver cannot process the metadata about region information or viewpoint information or does not use the metadata about region information or viewpoint information according to purpose, the adaptation set through which the metadata about region information or viewpoint information is transmitted may not be used (may be skipped). The segment may be delivered to the segment parser H26030.

The segment parser H26030 may parse the received segment and respectively deliver a video bitstream and metadata (DIRC metadata) about region information or viewpoint information to the video decoder H26040 and the DIRC parser H26050. The segment parser H26030 may be functionally classified according to parsing target. That is, the segment parser H26030 may be classified into a segment parser for parsing a segment for video and a segment parser for metadata about region information or viewpoint information.

The video decoder H26040 may decode the video bitstream and deliver the decoded video bitstream to the projector/renderer/sensors H26060.

The DIRC parser H26050 may parse the DIRC metadata and deliver the parsed information (DIRC info) to the projector/renderer/sensors H26060.

In addition, the DIRC parser H26050 may deliver the parsed information (DIRC info) to the DASH client H26010. The information (DIRC info) delivered to the DASH client H26010 may be used for the DASH client H26010 to select an adaptation set corresponding to a spatial region (tile) including the viewpoint or region intended by the producer.

The projector/renderer/sensors H26060 may receive the video bitstream from the video decoder H26040 and receive the DIRC metadata from the DIRC parser H26050. In addition, the projector/renderer/sensors H26060 may provide video data to a user using the DIRC information. A method through which the projector/renderer/sensors H26060 provide VR content to the user using the DIRC information may depend on application. For example, a viewpoint intended by a producer and indicated by DIRC can be displayed to the user through auto navigation. As another example, VR content can be displayed depending on the user's gaze with direction indication for guiding the viewpoint intended by the producer.

In the embodiments described with reference to FIGS. 24 to 26, an adaptation set for transmitting and signaling VR video and an adaptation set for transmitting and signaling metadata are separately present.

A description will be given of embodiments of transmitting and signaling VR video and metadata together in a single adaptation set with reference to FIGS. 27 to 29.

Embodiments of Transmitting Video and Metadata in Single Adaptation Set

Metadata about viewpoint information or region information may be transmitted together with VR video in a single adaptation set, distinguished from the cases described with reference to FIGS. 22 to 26. In this case, video data and metadata may be transmitted through a single file (segment or ISO BMFF). In a specific embodiment, VR video and metadata may be configured as separate tracks in a single file or configured as a single video file including the metadata.

An embodiment in which VR video and metadata are configured as separate tracks in a single file and an embodiment in which a single video track including the metadata is configured will be sequentially described below.

FIG. 27 illustrates an MPD which signals transmission of metadata about region information or viewpoint information according to another embodiment of the present invention.

The embodiment of FIG. 27 corresponds to the embodiment in which VR video and the metadata about region information or viewpoint information are configured as separate tracks in a single file. The VR video and the metadata about region information or viewpoint information are configured as separate tracks in a single adaptation set and a single file and transmitted.

In the embodiment of FIG. 27, the VR video track and the metadata track may be identified by ContentComponent which is a lower element of AdaptationSet in the MPD and may have contentType of “video” and “application” (H27010 and H27020). The ContentComponent may have Role as a lower element and the Role is used to indicate whether the VR video and/or the metadata (metadata about region information or viewpoint information) are transmitted through the aforementioned method of transmitting metadata through an additional adaptation set. That is, for VR video, “urn:mpeg:dash:role:2011” may be allocated to the role scheme and “main’ may be allocated to the value. In the case of metadata about region information or viewpoint information, “urn:mpeg:dash:role:201x” may be allocated to the role scheme and “dirc” may be allocated to the value or “urn:mpeg:dash:role:2011” may be allocated to the role scheme and “metadata” may be allocated to the value.

In the case of the embodiment of FIG. 27, “urn:mpeg:dash:role:2011” is allocated to the role scheme and “main” is allocated to the value for the VR video (H27030) and “urn:mpeg:dash:role:201x” is allocated to the role scheme and “dirc” is allocated to the value for the metadata about region information or viewpoint information (H27040).

FIG. 28 illustrates an MPD which signals transmission of metadata about region information or viewpoint information according to another embodiment of the present invention.

In the embodiment of FIG. 28, VR video and metadata about region information or viewpoint information are configured as a single track. The VR video and the metadata about region information or viewpoint information are configured as a single track in a single adaptation set and a single file.

A single file may basically include a single video track. The metadata about region information or viewpoint information may be stored in the form of metadata attached to a track such as sample group description. In this case, the MPD may include a single adaptation set including video and metadata and two roles for respectively indicating whether the video and the metadata are transmitted. That is, “urn:mpeg:dash:role:2011” may be allocated to the role scheme and “main” may be allocated to the value in the case of the VR video. In addition, “urn:mpeg:dash:role:201x” may be allocated to the role scheme and “dirc” may be allocated to the value or “urn:mpeg:dash:role:2011” may be allocated to the role scheme and “metadata” may be allocated to the value in the case of the metadata about region information or viewpoint information.

In the embodiment of FIG. 28, ContentComponent for identifying the VR video and the metadata is not present as a lower element of the Adaptation Set, distinguished from the embodiment of FIG. 27.

In the case of the embodiment of FIG. 28, “urn:mpeg:dash:role:2011” is allocated to the role scheme and “main” is allocated to the value for the VR video (H28030) and “urn:mpeg:dash:role:201x” is allocated to the role scheme and “dirc” is allocated to the value for the metadata about region information or viewpoint information (H28040).

A description will be given of receiver operation related to the method of transmitting and signaling metadata about region information or viewpoint information through a single adaptation set described above with reference to FIGS. 27 and 28.

FIG. 29 is a block diagram of a receiver according to another embodiment of the present invention.

Referring to FIG. 29, the receiver according to another embodiment of the present invention may include a DASH client H29020, a segment parser H29030, a video decoder H29040, a DIRC parser H29050 and/or a projector/renderer/sensors H29060.

An MPD, VR content and/or metadata about region information or viewpoint information may be provided by a DASH server H29010 and received by the DASH client H29020. Here, the DASH client H29020 of the receiver may receive VR content, MPD and/or metadata about region information or viewpoint information in a data packet format from the DASH server H29010. The DASH client H29020 may request the MPD, VR content and/or metadata about region information or viewpoint information from the DASH server H29010. The DASH client H29020 may generate an MPD and a segment from a received packet.

The DASH client H29020 may parse the received MPD to acquire information about content (VR content). Here, the DASH client H29020 may recognize presence or absence of the metadata about region information or viewpoint information through signaling with respect to an adaptation set through which the metadata about region information or viewpoint information is transmitted, described above with reference to FIGS. 27 and 28. In addition, the DASH client H29020 may activate the DIRC parser and the segment parser for DIRC depending on capabilities of the receiver and/or purpose of use of the content (refer to the dotted line of the figure). For example, when the receiver cannot process the metadata about region information or viewpoint information or does not use the metadata about region information or viewpoint information according to purpose, the adaptation set through which the metadata about region information or viewpoint information is transmitted may not be used (may be skipped). The segment may be delivered to the segment parser H29030.

The segment parser H29030 may parse the received segment and respectively deliver a video bitstream and metadata (DIRC metadata) about region information or viewpoint information to the video decoder H29040 and the DIRC parser H29050. The segment parser H29030 may be functionally classified according to parsing target. That is, the segment parser H29030 may be classified into a segment parser for parsing a segment for video and a segment parser for metadata about region information or viewpoint information.

The video decoder H29040 may decode the video bitstream and deliver the decoded video bitstream to the projector/renderer/sensors H29060.

The DIRC parser H29050 may parse the DIRC metadata and deliver the parsed information (DIRC info) to the projector/renderer/sensors H29060.

The projector/renderer/sensors H29060 may receive the video bitstream from the video decoder H29040 and receive the DIRC metadata from the DIRC parser H29050. In addition, the projector/renderer/sensors H29060 may provide video data to a user using the DIRC information. A method through which the projector/renderer/sensors H29060 provide VR content to the user using the DIRC information may depend on application. For example, a viewpoint intended by a producer and indicated by DIRC can be displayed to the user through auto navigation. As another example, VR content can be displayed depending on the viewpoint of the user with direction indication for guiding the viewpoint intended by the producer.

<Method of Transmitting and Signaling Metadata about Region Information or Viewpoint Information Using MPEG-2 TS>

The metadata about region information or viewpoint information described with reference to FIGS. 12 to 20 may be transmitted through an MPEG-2 TS. More specifically, the metadata about region information or viewpoint information may be transmitted through a packetized elementary stream packet (PES packet) or an adaptation field of a transport stream (TS).

An embodiment in which the metadata about region information or viewpoint information is transmitted through a PES packet having a unique PID and an embodiment in which the metadata about region information or viewpoint information is transmitted through an adaptation field of a TS will be sequentially described below.

Embodiment of Transmitting Metadata Through PES

According to an embodiment, the metadata about region information or viewpoint information may be transmitted through a PES packet through the following method. A stream ID stream_id of the PES packet including the metadata about region information or viewpoint information may be set to indicate a private stream and the stream type stream_type of the private stream may be set to indicate a metadata stream regarding region information or viewpoint information.

FIG. 30 illustrates a stream ID and information on a stream allocated to the stream ID, FIG. 31 illustrates a stream type and part of information on a stream allocated to the stream type, and FIG. 32 illustrates an access unit transmitted through a PES packet.

Referring to FIG. 30, when stream_id is “1011 1101”, a stream corresponding thereto indicates private_stream_1. When stream_id=“1011 1101” and stream_type is “0x27”, a stream (VR director's cut information stream) corresponding thereto is a stream related to the metadata about region information or viewpoint information (refer to note 11 of FIG. 30). Referring to FIG. 31, when stream_type is “0x27”, a stream corresponding thereto is a stream (VR director's cut information stream) related to the metadata about region information or viewpoint information.

FIG. 32 illustrates a configuration of an access unit transmitted through a single PES packet. The access unit (VDCI_AU) shown in FIG. 32 includes vdci_descriptor( ) and vdci_descriptor( ) may include the metadata about region information or viewpoint information. vdci_descriptor( ) will be described below.

Embodiment of Transmitting Metadata in Adaptation Field

According to an embodiment, the metadata about region information or viewpoint information may be transmitted through an adaptation field of a TS through the following method. When the metadata about region information or viewpoint information is included in the adaptation field and transmitted, presence or absence of a descriptor including the metadata about region information or viewpoint information may be indicated using a flag field, and when the flag field indicates presence of the descriptor including the metadata about region information or viewpoint information, the descriptor including the metadata about region information or viewpoint information may be included in the adaptation field.

FIG. 33 illustrates an adaptation field according to an embodiment of the present invention.

Referring to FIG. 33, the adaptation field includes vcdi_descriptor_not_present_flag. The vcdi_descriptor_not_present_flag indicates presence or absence of vcdi_descriptor( ). In the embodiment illustrated in FIG. 33, when the vcdi_descriptor_not_present_flag is set to 0, vcdi_descriptor( ) is present in adaptation_filed( ).

Whether a TS component can include the metadata about region information or viewpoint information in the adaptation field can be indicated through an extension descriptor. When extension_descriptor_tag is allocated to a preset value, the extension_descriptor_tag can indicate that the adaptation field of the component can include a descriptor with respect to the metadata about region information or viewpoint information.

FIG. 34 illustrates an extension descriptor according to an embodiment of the present invention, FIG. 35 illustrates values of an extension descriptor tag included in the extension descriptor and description of the values, and FIG. 36 illustrates a vdci extension descriptor according to an embodiment of the present invention.

Referring to FIG. 34, the extension descriptor according to an embodiment of the present invention may include a descriptor tag, a descriptor length and the extension descriptor tag and include a descriptor depending on a value of the extension descriptor tag.

The descriptor tag may indicate the present descriptor. In the embodiment illustrated in FIG. 34, the descriptor tag may be set to a value indicating the extension descriptor. In a specific embodiment, the descriptor tag may be set to “63” to indicate the extension descriptor. Here, a specific value of the descriptor tag may depend on embodiments.

The descriptor length may describe the length of the corresponding descriptor in bytes.

The extension descriptor tag may indicate a specific descriptor included in the extension descriptor.

Referring to FIG. 35, a value of the extension descriptor tag indicates a specific descriptor included in the extension descriptor. As illustrated in FIGS. 34 and 35, the extension descriptor includes an ObjectDescriptorUpdate descriptor when the extension descriptor tag is 0x02. The extension descriptor includes HEVC_timing_and_HRD_descriptor when the extension descriptor tag is 0x03. The extension descriptor includes af_extension_descriptor when the extension descriptor tag is 0x04. The extension descriptor includes vdci_extension_descriptor when the extension descriptor tag is 0x05.

FIG. 36 illustrates vdci_extension_descriptor according to an embodiment of the present invention.

The vdci_extenstions_descriptor according to an embodiment of the present invention may include a vdci descriptor type.

The vdci descriptor type indicates a type of a vdci descriptor which will be described below. For example, when the vdci descriptor type “0x01”, the vdci descriptor is 2d_vcdi_descriptor( ). When the vdci descriptor type is “0x02”, the vdci descriptor is spherical_vcdi_descriptor( ).

FIGS. 37 and 38 illustrate vdci descriptors according to an embodiment of the present invention.

More specifically, FIG. 37 illustrates a 2D vdci descriptor according to an embodiment of the present invention and FIG. 38 illustrates a spherical vcdi descriptor according to an embodiment of the present invention.

Referring to FIG. 37, a 2D vdci descriptor according to an embodiment of the present invention is shown.

2d_vcdi_descriptor may include 2d_vcdi_descr_tag, 2d_vdci_descr_length, reference_region_flag, duration_flag, next_vcdi_flag, reference_width, reference_height, top_left_x, top_left_y, width, height, interpolate, duration, next_top_left_x, next_top_left_y, next_width, next_height and/or next_interpolate.

2d_vcdi_descr_tag may identify the 2D vdci descriptor by allocating a unique value thereto.

The 2d_vdci_descr_length may indicate the length of the 2D vdci descriptor in bytes.

reference_region_flag may indicate presence or absence of reference_width and reference_height fields. In an embodiment, when the reference_region_flag is set to 1, the reference_region_flag may indicate presence of the reference_width and reference_height fields.

duration_flag may indicate presence or absence of a duration field. In an embodiment, the duration_flag may indicate presence of the duration field when set to 1.

next_vcdi_flag may indicate presence or absence of next_top_left_x, next_top_left_y, next_width and next_height fields. In an embodiment, next_vcdi_flag may indicate presence of the next_top_left_x, next_top_left_y, next_width and next_height fields when set to 1.

“duration” may indicate the duration of the current region. In another embodiment, “duration” may indicate a difference between a current region representation time and a next region representation time.

reference_width may indicate the horizontal size of a 2D space. Here, the horizontal size of the 2D space may be represented by the number of pixels.

reference_height may indicate the vertical size of the 2D space. Here, the vertical size of the 2D space may be represented by the number of pixels.

top_left_x may indicate the horizontal coordinate of the top left point of a region to be represented.

top_left_y may indicate the vertical coordinate of the top left point of the region to be represented.

“width” may indicate the horizontal size of the region to be represented. Here, the horizontal size of the region to be represented may be represented in number of pixels.

“height” may indicate the vertical size of the region to be represented. Here, the vertical size of the region to be represented may be represented in number of pixels.

“interpolate” may indicate whether values between the previous region and the current region are filled by linearly interpolated values. In an embodiment, when interpolate is 1, the values between the previous region and the current region can be filled by linearly interpolated values.

next_top_left_x may indicate the horizontal coordinate of the top left point of the next region to be represented.

next_top_left_y may indicate the vertical coordinate of the top left point of the next region to be represented.

The next_width may indicate the horizontal size of the next region to be represented. Here, the horizontal size of the region to be represented may be represented in number of pixels.

The next_height may indicate the vertical size of the next region to be represented. Here, the vertical size of the region to be represented may be represented in number of pixels.

The next_interpolate may indicate whether values between the current region and the next region are filled by linearly interpolated values. In an embodiment, when the next_interpolate is 1, the values between the current region and the next region can be filled by linearly interpolated values.

Referring to FIG. 38, a spherical vdci descriptor according to an embodiment of the present invention is shown.

spherical_vcdi_descriptor may include spherical_vcdi_descr_tag, spherical_vdci_descr_length, reference_region_flag, duration_flag, next_vcdi_flag, reference_min_yaw, reference_max_yaw, reference_min_pitch, reference_max_pitch, yaw, pitch, roll, field_of_view, interpolate, duration, next_yaw, next_pitch, next_roll, next_field_of_view and/or next_interpolate.

spherical_vcdi_descr_tag may indicate the spherical vdci descriptor by allocating a unique value thereto.

spherical_vdci_descr_length may indicate the length of the spherical vdci descriptor in bytes.

reference_region_flag may indicate presence or absence of reference_min_yaw, reference_max_yaw, reference_min_pitch and reference_max_pitch fields. In an embodiment, the reference_region_flag may indicate presence of the reference_min_yaw, reference_max_yaw, reference_min_pitch and reference_max_pitch fields when set to 1.

duration_flag may indicate presence or absence of the duration field. In an embodiment, the duration_flag may indicate presence of the duration field when set to 1.

next_vcdi_flag may indicate presence or absence of next_yaw, next_pitch, next_roll, next_field_of view and next_interpolate fields. In an embodiment, the next_vcdi_flag may indicate presence of the next_yaw, next_pitch, next_roll, next_field_of_view and next_interpolate fields when set to 1.

“duration” may indicate the duration of the current region. Alternatively, the duration may indicate a difference between a current region representation time and a next region representation time.

reference_min_yaw may indicate a minimum value of a rotation amount with respect to the yaw axis of a 3D space.

reference_max_yaw may indicate a maximum value of the rotation amount with respect to the yaw axis of the 3D space.

reference_min_pitch may indicate a minimum value of a rotation amount with respect to the pitch axis of the 3D space.

reference_max_pitch may indicate a maximum value of the rotation amount with respect to the pitch axis of the 3D space.

“yaw” may indicate a rotation amount with respect to the yaw axis of a region to be represented.

“pitch” may indicate a rotation amount with respect to the pitch axis of the region to be represented.

“roll” may indicate a rotation amount with respect to the roll axis of the region to be represented.

field_of_view may indicate a field of view of the region to be represented.

“interpolate” may indicate whether values between the previous region and the current region are filled by linearly interpolated values. In an embodiment, when interpolate is 1, the values between the previous region and the current region can be filled by linearly interpolated values.

next_yaw may indicate a rotation amount with respect to the yaw axis of the next region to be represented.

next_pitch may indicate a rotation amount with respect to the pitch axis of the next region to be represented.

next_roll may indicate a rotation amount with respect to the roll axis of the next region to be represented.

next_field_of_view may indicate a field of view of the next region to be represented.

next_interpolate may indicate whether values between the current region and the next region are filled by linearly interpolated values. In an embodiment, when interpolate is 1, the values between the current region and the next region can be filled by linearly interpolated values.

2D vdci descriptor and spherical_vcdi_descriptor shown in FIGS. 37 and 38 are specific examples of the metadata about region information or viewpoint information in a 2D space and the metadata about region information or viewpoint information in a 3D space, respectively. The metadata information described with reference to FIGS. 12 to 20 may be selectively included in the descriptor, and the information included in the descriptor of this embodiment may be omitted

Hereinafter, a description will be given of receiver operation related to the methods of transmitting and signaling metadata about region information or viewpoint information through an MPEG-2 TS described above with reference to FIGS. 29 to 38.

FIG. 39 is a block diagram of a receiver according to another embodiment of the present invention.

Referring to FIG. 39, the receiver according to another embodiment of the present invention may include an MPEG-2 TS receiver H39020, a video decoder H39030, a DIRC parser H39040 and/or a projector/renderer/sensors H39050.

VR content and/or metadata about region information or viewpoint information may be provided by an MPEG-2 TS transmitter H39010 and received by the MPEG-2 TS receiver H39020. Here, the MPEG-2 TS receiver H39020 of the receiver may receive VR content and/or metadata about region information or viewpoint information in a packet format from the MPEG-2 TS transmitter H39010. The MPEG-2 TS receiver H39020 may analyze received MPEG-2 TS packets to generate a video bitstream and metadata about region information or viewpoint information (DIRC metadata).

Here, the MPEG-2 TS receiver H39020 may recognize presence or absence of the metadata through the aforementioned method of identifying the metadata about region information or viewpoint information transmitted through a PEG or an adaptation field.

In addition, the MPEG-2 receiver H39020 may activate the DIRC parser depending on capabilities of the receiver and/or purpose of use of the content (refer to the dotted line of the figure). For example, when the receiver cannot process the metadata about region information or viewpoint information or does not use the metadata about region information or viewpoint information according to purpose, the adaptation set through which the metadata about region information or viewpoint information is transmitted may not be used (may be skipped). The MPEG-2 receiver H39020 may deliver the video bitstream and the metadata about region information or viewpoint information (DIRC metadata) to the video decoder H39030 and the DIRC parser H39040.

The video decoder H39030 may decode the video bitstream and deliver the decoded video bitstream to the projector/renderer/sensors H39050.

The DIRC parser H39040 may parse the DIRC metadata and deliver the parsed information (DIRC info) to the projector/renderer/sensors H39050.

The projector/renderer/sensors H39050 may receive the video bitstream from the video decoder H39030 and receive the DIRC metadata from the DIRC parser H39040. In addition, the projector/renderer/sensors H39050 may provide video data to a user using the DIRC information. A method through which the projector/renderer/sensors H39050 provide VR content to the user using the DIRC information may depend on application. For example, a viewpoint intended by a producer and indicated by DIRC can be displayed to the user through auto navigation. As another example, VR content can be displayed depending on the viewpoint of the user with direction indication for guiding the viewpoint intended by the producer.

<Method of Transmitting and Signaling Metadata about Region Information or Viewpoint Information Using Video Coding Layer>

The metadata about region information or viewpoint information described above with reference to FIGS. 12 to 20 may be transmitted through a video coding layer (VCL). More specifically, the metadata about region information or viewpoint information may be transmitted in the form of a VCL SEI (Supplemental Enhancement Information) message.

FIG. 40 illustrates metadata about region information or viewpoint information which is included in an SEI message according to an embodiment of the present invention.

Referring to the upper part of FIG. 40, a payload of an SEI message according to an embodiment of the present invention includes metadata about region information or viewpoint information in a 2D space.

The payload of the SEI message according to an embodiment of the present invention may include directors_cut_id, reference_region_flag, duration_flag, next_vcdi_flag, reference_width, reference_height, top_left_x, top_left_y, width, height, interpolate, duration, next_top_left_x, next_top_left_y, next_width, next_height and/or next_interpolate.

The directors_cut_id may indicate a unique ID of the metadata about region information or viewpoint information in the 2D space. When there are pieces of metadata about region information or viewpoint information in multiple 2D spaces in the same stream, the directors_cut_id may be used to identify each piece of the metadata. That is, pieces of metadata having the same directors_cut_id form a metadata sequence indicating region information or viewpoint information in a single 2D space.

Description of the 2d_vcdi_descriptor( ) with reference to FIG. 33 may be applied to other fields included in the payload of the SEI message according to an embodiment of the present invention.

Referring to the lower part of FIG. 40, a payload of an SEI message according to another embodiment of the present invention includes metadata about region information or viewpoint information in a 3D space.

The payload of the SEI message according to another embodiment of the present invention may include directors_cut_id, reference_region_flag, duration_flag, next_vcdi_flag, reference_min_yaw, reference_max_yaw, reference_min_pitch, reference_max_pitch, yaw, pitch, roll, field_of_view, interpolate, duration, next_yaw, next_pitch, next_roll, next_field_of_view and/or next_interpolate.

The directors_cut_id may indicate a unique ID of the metadata about region information or viewpoint information in the 3D space. When there are pieces of metadata about region information or viewpoint information in multiple 3D spaces in the same stream, the directors_cut_id may be used to identify each piece of the metadata. That is, pieces of metadata having the same directors_cut_id form a metadata sequence indicating region information or viewpoint information in a single 3D space.

Description of the spherical_vcdi_descriptor( ) with reference to FIG. 34 may be applied to other fields included in the payload of the SEI message according to an embodiment of the present invention.

FIG. 41 illustrates metadata about region information or viewpoint information included in an SEI message according to another embodiment of the present invention.

The metadata according to another embodiment of the present invention shown in FIG. 41 includes metadata about region information or viewpoint information in a 3D space.

The SEI message according to another embodiment of the present invention may set the boundaries of one or more regions by the four great circles described above. That is, the SEI message may set the boundaries in a manner corresponding to the case where “region type” is 1 in FIGS. 16 to 19.

Here, the set region may be a recommended viewport for display.

Referring to FIG. 41, the payload of the SEI message in accordance with another embodiment of the present invention may include omni_viewport_id, omni_viewport_cancel_flag, omni_viewport_persistence_flag, omni_viewport_cnt_minus1, omni_viewport_yaw_center, omni_viewport_pitch_center, omni_viewport_roll_center, omni_viewport_yaw_range and/or omni_viewport_pitch_range.

omni_viewport_id may indicate an identification number that identifies one or more regions. In a more specific embodiment, omni_viewport_id may indicate an identification number that may be used to identify the purpose of a recommended viewport region.

omni_viewport_cancel_flag may indicate persistence of the previous omnidirectional viewport SEI message. In an embodiment, if omni_viewport_cancel_flag is 1, persistence of the previous omnidirectional viewport SEI message may be canceled. If omni_viewport_cancel_flag is 0, this may indicate that the omnidirectional viewport SEI message continues.

omni_viewport_persistence_flag may indicate persistence of an omnidirectional viewport SEI message for the current layer. In an embodiment, if omni_viewport_persistence_flag is 0, this may indicate that the omnidirectional viewport SEI message is applied to the current decoded picture only. If omni_viewport_persistence_flag is 1, this may indicate that the omnidirectional viewport SEI message is applied for the current layer. Even if omni_viewport_persistence_flag is 1, the omnidirectional viewport SEI message may be set not to be applied any longer if a predetermined condition is satisfied.

omni_viewport_cnt_minus1 may indicate the number of regions indicated by the SEI message. In a more specific embodiment, omni_viewport_cnt_minus1 may indicate the number of recommended viewport regions indicated by the SEI message.

omni_viewport_yaw_center may indicate the yaw value of the center point of the corresponding region. In a more specific embodiment, omni_viewport_yaw_center[i] may indicate the yaw value of the center point of the i-th region, which may be a recommended viewport region.

omni_viewport_pitch_center may indicate the pitch value of the center point of the corresponding region. In a more specific embodiment, omni_viewport_pitch_center[i] may indicate the pitch value of the center point of the i-th region, which may be a recommended viewport region.

omni_viewport_roll_center may indicate the roll value of the center point of the corresponding region. In a more specific embodiment, omni_viewport_roll_center[i] may indicate the roll value of the center point of the i-th region, which may be a recommended viewport region.

omni_viewport_yaw_range may indicate the range or size of the region through the yaw value. In a more specific embodiment, omni_viewport_yaw_range[i] may indicate the range or size of the i-th region through the yaw value, where the region may be a recommended viewport region.

omni_viewport_pitch_range may indicate the range or size of the region through the pitch value. In a more specific embodiment, omni_viewport_pitch_range[i] may indicate the range or size of the i-th region through the pitch value, where the region may be a recommended viewport region.

vr_2d_directors_cut (payloadSize) shown in FIG. 40 is a specific example of the metadata about the region information or the viewpoint information in the 2D space, and vr_2d_directors_cut (payloadSize) and omnidirectional_viewport (payloadSize) shown in FIGS. 40 and 41 are specific examples of the metadata about the region information or the viewpoint information in the 3D space. The metadata information described in FIGS. 12 to 20 may be optionally included in the SEI message, and the information included in the SEI message may be optionally omitted.

Hereinafter, a description will be given of receiver operation related to the method of transmitting and signaling metadata about region information or viewpoint information through the VCL described above with reference to FIGS. 40 and 41.

FIG. 42 is a block diagram of a receiver according to another embodiment of the present invention.

Referring to FIG. 42, the receiver according to another embodiment of the present invention may include a network client/content parser H42020, a video decoder H42030, a DIRC parser H42040 and/or a projector/renderer/sensors H42050.

Video data including VR content and/or metadata about region information or viewpoint information may be provided by a content/network server H42010 and received by the network client/content parser H42020. Here, the network client/content parser H42020 of the receiver may receive video data in the form of a network packet or a file from the content/network server H42010. The network client/content parser H42020 may analyze the received network packet or file to generate a video bitstream.

The network client/content parser H42020 may deliver the video bitstream to the video decoder H42030.

The video decoder H42030 may decode the video bitstream. The video decoder H42030 may decode the video bitstream to acquire video data and metadata about region information or viewpoint information (DIRC metadata).

The video decoder H42030 may deliver the video bitstream to the projector/renderer/sensors H42050.

In addition, the video decoder H42030 may activate the DIRC parser H42040 depending on capabilities of the receiver and/or purpose of use of the content and deliver the metadata about region information or viewpoint information (DIRC metadata) to the DRIC parser H42040. For example, when the receiver cannot process the metadata about region information or viewpoint information or does not use the metadata about region information or viewpoint information according to purpose, the adaptation set through which the metadata about region information or viewpoint information is transmitted may not be used (may be skipped).

The DIRC parser H42040 may parse the DIRC metadata and deliver the parsed information (DIRC info) to the projector/renderer/sensors H42050.

The projector/renderer/sensors H42050 may receive the video bitstream from the video decoder H42030 and receive the DIRC metadata from the DIRC parser H42040. In addition, the projector/renderer/sensors H42050 may provide video data to a user using the DIRC information. A method through which the projector/renderer/sensors H42050 provide VR content to the user using the DIRC information may depend on application. For example, a viewpoint intended by a producer and indicated by DIRC can be displayed to the user through auto navigation. As another example, VR content can be displayed depending on the viewpoint of the user with direction indication for guiding the viewpoint intended by the producer.

<Content Transmission and Reception Process and Metadata for 360-degree Video Service>

FIG. 43 is a diagram illustrating a process of transmitting and receiving content and metadata about a 360-degree video service according to an embodiment of the present invention.

Referring to FIG. 43, configurations of a transmission side and a reception side for transmitting and receiving content and metadata about a 360-degree video service are shown. Here, the transmission side configuration may be included in a 360-degree video transmission device, and the reception side configuration may be included in a 360-degree video reception device. The transmission side configuration and process may include a configuration and a process for generating a 360-degree video.

Hereinafter, a process of transmitting and receiving content and metadata about a 360-degree video service will be described with reference to FIG. 43.

First, a 360-degree video transmission device may generate one or more images (input images) captured in various directions using one or more cameras (SH43010). Here, the 360-degree video transmission device may capture an omnidirectional (360-degree) image. As such, the process of capturing images in multiple directions may be referred to as an acquisition process.

Next, the 360-degree video transmission device may stitch the captured images onto a 3D geometry (SH43020). Here, the 3D geometry may be a sphere, a cube, or the like. The stitching process may be a process of creating a panoramic image or a spherical image by connecting a plurality of captured images on a 3D geometry. In this embodiment, a spherical image is generated through image stitching.

Next, the 360-degree video transmission device may generate rendering metadata about the rendering characteristic of the 360-degree video (VR video) (SH43030). Thus, the process of generating rendering metadata about a 360-degree video (VR video) may be referred to as an authoring process.

Next, the 360-degree video transmission device may project a stitched image onto a projection format, which is a formal geometry, to form a rectangular frame (packed frame, packed image) (projection/mapping, SH43040).

The process may be subdivided into a projection process of projecting an image onto a projection format, which is a formal geometry, and creating a projected frame (a projected image) and a mapping process of mapping the projected frame (projected image) onto a packed frame (packed image).

Here, the projection format may be equirectangular projection, cubic projection, or the like. The stitched image may be projected onto a 2D frame through the projection process.

In addition, in the mapping process, a packed frame may be configured by adjusting the arrangement and/or resolution of the rectangular regions constituting the projected frame. At this time, it is also possible to increase the quality of a specific region. Here, the specific region may be a specific user viewpoint region, or may be the producer's intended viewpoint region described above.

This mapping process may be referred to as a region-by-region packing process. The region-by-region packing process may be selectively performed. If the region-by-region packing process is not performed, the projected frame (projected image) may be the same as the packed frame (packed image).

The 360-degree video transmission device may generate metadata about the projection characteristic and/or mapping characteristic in the projection/mapping process.

Next, the 360-degree video transmission device may generate a coded video picture by encoding the packed frame (packed image) (video encoding, SH 43050).

Next, the 360-degree video transmission device may generate a file or a segment including the coded video picture (SH 43060). In this embodiment, the 360-degree video transmission device transmits a file or segment including rendering metadata and projection/mapping metadata as well as the coded video picture.

The 360-degree video transmission device may generate DASH (Dynamic Adaptive Streaming over HTTP) MPS (Media Presentation Description) and send the MPD and the segment (SH43070).

The 360-degree video reception device may receive and parse the DASH MPD, and request and receive a segment (SH43080).

The 360-degree video reception device may receive a file or segment and extract a coded video picture from the file or segment (SH43090). In this embodiment, rendering metadata and projection/mapping metadata are included in the file or segment. Therefore, the 360-degree video reception device may extract the rendering metadata and projection/mapping metadata and parse the metadata.

Next, the 360-degree video reception device may generate a packed frame by decoding the coded video picture (SH43100).

Next, the 360-degree video reception device may restore an image of a three-dimensional geometry from the packed frame (packed image). In this embodiment, the 360-degree video reception device may restore a spherical image of a three-dimensional geometry from the packed frame (packed image) (SH43110). At this time, the 360-degree video reception device may restore a three-dimensional image using the projection/mapping metadata.

Next, the 360-degree video reception device may render the image (spherical image) of a three-dimensional geometry in a three-dimensional space (SH43130). At this time, the 360-degree video reception device may render the three-dimensional image in a three-dimensional space using the rendering metadata.

Further, the 360-degree video reception device may render the three-dimensional image in the three-dimensional space by additionally using user viewport information, which will be described later.

Next, the 360-degree video reception device may present the image in the three-dimensional space on the display (SH43140).

The 360-degree video reception device may track the user viewport information by detecting movement of the user's head/eyes during operation (SH43120). The tracked user viewport information may be generated in real time and used in the process of rendering a 360-degree video.

This user viewport information may also be used in processes other than the process of rendering the 360-degree video. For example, if view-dependent processing is applied, each step may be performed depending on user viewport information.

Specifically, video decoding may be performed on the video data related to the region including the user viewport, depending on the user viewport information (case A).

Alternatively, decapsulation may be performed on a file or segment related to the region including the user viewport depending on the user viewport information (case B).

Alternatively, reception of a segment related to the region including the user viewport may be performed depending on the user viewport information, (case C).

Hereinafter, information that may be included in the rendering metadata and projection/mapping metadata described in FIG. 43 will be described with reference to FIG. 44.

FIG. 44 illustrates an example of information included in rendering metadata and projection/mapping metadata according to an embodiment of the present invention.

According to an embodiment, the rendering metadata may include vr_mapping_type, center_yaw, center_pitch, min_yaw, max_yaw, min_pitch, max_pitch, Region Mapping Information (i.e., EquiMapVideoInfoBox, CubeMapVideoInfoBox) and/or stereo mode.

vr_mapping_type may indicate information about a mapping type of mapping of a 360-degree video. According to an embodiment, if the value of vr_mapping_type is 0, this may indicate “equirectangular” as a mapping type. If the value of vr_mapping_type is 1, this may indicate “cubic” as a mapping type. If the value of vr_mapping_type is 2, this may indicate “cylinder” or “panorama” as a mapping type. If the value of vr_mapping_type is 3, this may indicate “pyramid” as a mapping type.

In other words, the vr_mapping_type information may indicate a projection scheme used in mapping a 360-degree video onto a 2D image (frame). In the above embodiment, if the value of vr_mapping_type is 0, this may indicate that equirectangular projection is used. If the value of vr_mapping_type is 1, this may indicate that cubic projection is used. If the value of vr_mapping_type is 2, this may indicate that cylinder projection or panorama projection is used. If the value of vr_mapping_type is 3, this may indicate that pyramid projection is used.

The center_yaw field may provide information related to the center pixel of the 2D image onto which the 360-degree video data is projected and the center point in the 3D space. In an embodiment, the center_yaw field may indicate the degree of rotation of the center point of the 3D space with respect to the origin of the capture space coordinate system or the origin of the global coordinate system. In this embodiment, the center_yaw field may indicate the degree of rotation as a yaw value.

The center_pitch field may provide information related to the center pixel of a 2D image onto which the 360-degree video data is projected and the center point in the 3D space. In an embodiment, the center_pitch field may indicate the degree of rotation of the center point of the 3D space with respect to the origin of the capture space coordinate system or the origin of the global coordinate system. In this embodiment, the center_pitch field may indicate the degree of rotation as a pitch value.

The min_yaw field may indicate a region occupied in the 3D space with the minimum value of yaw. This field may indicate the minimum value of the amount of rotation about the yaw axis.

The max_yaw field may indicate a region occupied in the 3D space with the maximum value of yaw. This field may indicate the maximum value of the amount of rotation about the yaw axis.

The min_pitch field may indicate a region occupied in the 3D space with the minimum value of pitch. This field may indicate the minimum value of the amount of rotation about the pitch axis.

The max_pitch field may indicate a region occupied in the 3D space with the maximum value of pitch. This field may indicate the maximum value of the amount of rotation with respect to the pitch axis.

Region Mapping Information (i.e., EquiMapVideoInfoBox, CubeMapVideoInfoBox) may indicate a mapping relationship between a projected picture which is a result of projection of the 360-degree video onto the 2D domain, and the regions constituting a packed picture actually used as an input of the encoder. Alternatively, Region Mapping Information (i.e., EquiMapVideoInfoBox, CubeMapVideoInfoBox) may indicate a mapping relationship between the regions constituting the packed picture and spherical regions in the 3D domain.

The stereo mode field may indicate a 3D layout supported by a 360-degree video. In addition, the stereo mode field may indicate whether the 360-degree video supports 3D. In an embodiment, if the value of the stereo mode field is 0, the 360-degree video may be in a monoscopic mode. That is, the projected 2D image may contain only one monoscopic view. In this case, the 360-degree video may not support 3D.

If the stereo mode field value is 1 or 2, the 360-degree video may conform to the Left-Right layout and the Top-Bottom layout. The Left-Right layout and the Top-Bottom layout may be referred to as a side-by-side format and a top-bottom format, respectively. In the case of the Left-Right layout, 2D images onto which the left image/right image are projected may be horizontally arranged in the image frame. In the case of the Top-Bottom layout, 2D images onto which the left image/right image are projected may be vertically arranged in the image frame. If the stereo mode field has other values, it may be reserved for future use.

Next, rendering metadata according to an embodiment of the present invention may include initial_yaw, initial_pitch, initial_roll, viewport_vfov and/or viewport_hfov.

The rendering metadata according to an embodiment of the present invention may include information related to an initial viewpoint. The information on the initial viewpoint may refer to the initial view related metadata of FIG. 8.

The initial_yaw, initial_pitch, and initial_roll fields may indicate an initial time of reproduction of a 360-degree video. That is, the center point of the viewport which is initially displayed at the time of reproduction, may be indicated by these three fields.

The initial_yaw field may indicate the position of the center point in reproduction of the 360-degree video by a direction (sign) and degree (angle) of rotation about the yaw axis.

The initial_pitch field may indicate the position of the center point in reproduction of the 360-degree video by a direction (sign) and degree (angle) of rotation about the pitch axis.

The initial_roll field may indicate the position of the center point in reproduction of the 360-degree video by a direction (sign) and degree (angle) of rotation about the roll axis.

viewport_vfov may indicate the value of the vertical field of view of the viewport. In an embodiment, viewport_vfov may be a vertical field of view with the initial_pitch as a reference (center).

viewport_hfov may indicate the value of the horizontal field of view of the viewport. In an embodiment, viewport_hfov may be a horizontal field of view with reference to initial_yaw (center).

In another embodiment, the rendering metadata may provide ROI (Region Of Interest)-related information as well as information about the initial viewpoint. The ROI related information may refer to the ROI-related metadata of FIG. 8 and may be used to indicate a recommended region. In addition, the ROI-related information may be used to indicate the producer intended region or the like.

The projection/mapping metadata described in FIG. 43 may take a box form as shown in FIG. 45 and be included in a file.

FIG. 45 illustrates a box including projection/mapping metadata according to another embodiment of the present invention.

A vrvd box according to an embodiment of the present invention may include global_yaw, global_pitch, global_roll, projection_format, format_uri, mapping_flag, num_regions, pf_width, pf_height, quality_ranking, pf_reg_width, pf_reg_height, pf_reg_top, pf_reg_left, pf_reg_min_yaw, pf_reg_max_yaw, pf_reg_min_pitch, pf_reg_max_pitch, pf_reg_roll, rect_width, rect_height, rect_top, rect_left, and/or rect_rotation.

global_yaw, global_pitch, and global_roll may describe the yaw, pitch, and roll of the projection, respectively. More specifically, global_yaw, global_pitch, and global_roll may describe the yaw, pitch, and roll of a 3D rendering model corresponding to the projected frame.

In an embodiment, global_yaw, global_pitch, and global_roll may describe the yaw, pitch, and roll of the projection in degree units of fixed decimal point of 16.16 based on the global coordinate system.

projection_format may describe the projection format. In an embodiment, projection_format may describe the projection format as listed in [CICP: Coding independent media description code points].

format_uri may describe a URI that defines projection_format. In an embodiment, format_uri may describe a URI that defines projection_format as a NULL termination string of UTF-8 characters.

mapping_flag may indicate whether region-wise mapping or region-wise packing is applied. In an embodiment, if mapping_flag is 0, this may indicate that region-wise mapping or region-wise packing is not applied. If mapping_flag is 1, this may indicate that region-wise mapping or region-wise packing is applied.

If the region-wise mapping or the region-wise packing is not applied, the packed frame may have the same presentation format as the projected frame. In this case, regions may be specified and quality ranking may be described.

num_regions may indicate the number of regions mapped to the packed frame in the projected frame. In an embodiment, if num_regions is 0, the packed frame may have the same presentation format as the projected frame.

pf_width and pf_height may describe the width and height of the projected frame, respectively.

quality_ranking may describe the quality ranking of a region. In an embodiment, if quality_ranking is 0, this may indicate that the quality rank is undefined. In an embodiment, if quality_ranking[i] is less than quality_ranking[j], this may indicate that the region indicated by index i has a higher quality than the region indicated by index j.

pf_reg_width may describe the width of a region. More specifically, pf_reg_width[i] may describe the width of the i-th region.

In an embodiment, if i is less than num_regions−1, then pf_reg_width[i] may not be 0.

pf_reg_width[num_regions−1] may be 0. If pf_reg_width[num_regions−1] is 0, mapping_flag should be equal to 1, and the (num_regions−1)-th region (a region having i=num_regions−1) includes all areas not covered by the previous region (a region having i<num_region−1) in the projected frame.

pf_reg_height may describe the height of a region. More specifically, pf_reg_height[i] may describe the height of the i-th region.

pf_rect_top and pf_reg_left may describe the top sample row and the leftmost sample column of a region in the projected frame. More specifically, pf_rect_top[i] and pf_reg_left[i] may describe the top sample row and the leftmost sample column of the i-th region of the projected frame. In an embodiment, pf_rect_top may have a value greater than or equal to 0 and less than pf_height, and pf_reg_left may have a value greater than or equal to 0 and less than pf_width. Here, 0 may mean the top-left corner of the projected frame.

pf_reg_min_yaw and pf_reg_max_yaw may indicate the minimum value and the maximum value of yaw of a 3D rendering model corresponding to a region of the projected frame, respectively. More specifically, pf_reg_min_yaw[i] and pf_reg_max_yaw[i] may indicate the minimum value and the maximum value of yaw of a 3D rendering model corresponding to the i-th region of the projected frame, respectively.

pf_reg_min_pitch and pf_reg_max_pitch may indicate the minimum value and the maximum value of pitch of a 3D rendering model corresponding to a region of the projected frame, respectively. More specifically, pf_reg_min_pitch[i] and pf_reg_max_pitch[i] may indicate the minimum value and the maximum value of pitch of a 3D rendering model corresponding to the i-th region of the projected frame, respectively.

pf_reg_roll may indicate the roll value of a 3D rendering model corresponding to a region of the projected frame. More specifically, pf_reg_roll[i] may indicate the roll value of the 3D rendering model corresponding to the i-th region of the projected frame.

rect_width, rect_height, rect_top, and rect_left may describe the width, height, top sample row, and leftmost sample column of a region in the packed frame, respectively. More specifically, rect_width[i], rect_height[i], rect_top[i], and rect_left[i] may describe the width, height, top sample row, and leftmost sample column of the i-th region in the packed frame.

rect_rotation may describe the rotation value of a region in the packed frame. More specifically, rect_rotation[i] may describe the value of rotation of the i-th region about the center of the i-th region in the packed frame.

<Method of Transmitting and Receiving ROI Metadata for Producer Intended Viewpoint/Region, Statistically Preferred Viewpoint/Region>

Hereinafter, a method of transmitting/receiving ROI metadata about the producer intended viewpoint/region and statistically preferred viewpoint/region, and a specific transmission/reception operation process will be described.

Information on the producer intended viewpoint/region (the director's cut), the statistically preferred viewpoint/region (the most-interesting regions) in the VR video service may be transmitted in the form of ROI metadata. In both cases, the transmitting and receiving operations may be performed as follows.

FIG. 46 is a diagram illustrating a process of transmitting and receiving content and metadata about a 360-degree video service according to another embodiment of the present invention.

The basics of the process of transmitting and receiving the content and metadata about the 360-degree video service shown in FIG. 46 may be substantially the same as those described above with reference to FIG. 43. Therefore, differences will be mainly described below.

The ROI metadata according to an embodiment may transmit information on the producer intended viewpoint/region (director's cut) indicating the viewport and/or direction intended by the producer.

Such information on the producer intended viewpoint/region (director's cut) may be information determined according to the intention of the director or the content producer during or after production.

Such information on the producer intended viewpoint/region (director's cut) may be used to render a VR video in a manner specified for an application in the user device.

The viewport and/or rotation information included in the information on the producer intended viewpoint/region (director's cut) may be presented in spherical coordinates.

The information on the producer intended viewpoint/region (director's cut) may be edited before the projection/mapping process and transmitted to the reception side. In the user equipment on the reception side, the information on the producer intended viewpoint/region (director's cut) may be used after the re-projection/mapping process. That is, the information on the producer intended viewpoint/region (director's cut) may be applied to a 3D model (spherical surface image) for VR video rendering.

Since editing and use of the information on the producer intended viewpoint/region (director's cut) are performed in the 3D model (spherical surface image), information more intuitive than a two-dimensional packed frame or a coded video picture may be provided. Thus, the producer may easily edit the information on the producer intended viewpoint/region (director's cut), and the user device may also easily render a VR image.

FIG. 47 is a diagram illustrating a process of transmitting and receiving content and metadata about a 360-degree video service according to another embodiment of the present invention.

The basics of the process of transmitting and receiving the content and metadata about the 360-degree video service shown in FIG. 47 may be substantially the same as those described above with reference to FIG. 43. Therefore, differences will be mainly described below.

The ROI metadata according to another embodiment may transmit information on statistically preferred viewpoints/regions (most-interesting regions). The information on statistically preferred viewpoints/regions (most-interesting regions) may be used for data prefetching in VR video prefetching.

The information on statistically preferred viewpoints/regions (most-interesting regions) may be derived from user statistics by the service/content provider or may be determined by prediction by the service/content provider.

The information on statistically preferred viewpoints/regions (most-interesting regions) may be used for a user device to select data to be requested for the purpose of prefetching.

The information on statistically preferred viewpoints/regions (most-interesting regions) may be edited before the projection/mapping process and transmitted to the reception side. In addition, the viewport and/or rotation information included in the statistically preferred viewpoints/regions (most-interesting regions) may be presented in spherical coordinates in the same manner as the information on the producer intended viewpoint/region (director's cut).

The information on the statistically preferred viewpoints/regions (most-interesting regions) may be used to determine a segment for which a user device will request prefetching. That is, the information on statistically preferred viewpoints/regions (most-interesting regions) may be used in the process of receiving the DASH MPD and segment.

While ROI metadata of 2D Cartesian coordinates is ineffective in describing segments of each face of a cube, spherical coordinates may be advantageous in describing ROI metadata as continuous segments. However, since the projection format is not limited to a sphere, other projection formats may be applied.

The syntax and semantics of the metadata used in the ROI metadata transmission/reception process described above may be given as shown in FIG. 48.

FIG. 48 illustrates ROI metadata according to an embodiment of the present invention.

The ROI metadata track may be linked to a track describing the same via a ‘cdsc (content describes)’ track reference.

The media track connected to the metadata track may be connected to another media track through a ‘tref’ box.

The SphericalCoordinates sample entry (‘sphc’) provides spatial information associated with the referenced track, and the referenced track is represented by a spherical coordinate system.

Referring to the top of FIG. 48, the SphericalCoordinates sample entry may include reference_min_yaw, reference_max_yaw, reference_min_pitch and reference_max_pitch.

reference_min_yaw, reference_max_yaw, reference_min_pitch and reference_max_pitch may provide the range of yaw and pitch values in degrees in a reference spherical space in which all ROI coordinates (yaw, pitch, roll, and field_of_view) are calculated.

reference_min_yaw may indicate the minimum value of yaw in the reference spherical space.

reference_max_yaw may indicate the maximum value of yaw in the reference spherical space.

reference_min_pitch may indicate the minimum value of pitch in the reference spherical space.

reference_max_pitch may indicate the minimum value of pitch in the reference spherical space.

The spherical coordinates sample associated with the SphericalCoordinates sample entry complies with the syntax as shown at the bottom of FIG. 48.

Referring to the bottom of FIG. 48, a spherical coordinates sample may include yaw, pitch, roll, field_of_view, duration and/or interpolate.

“yaw” may indicate the angle of rotation in degrees of the center point of the region associated with the media sample of the referenced track about the yaw axis.

“pitch” may indicate the angle of rotation in degrees of the center point of the region associated with the media sample of the referenced track about the pitch axis.

“roll” may indicate the angle of rotation in degrees of the center point of the region associated with the media sample of the referenced track about the roll axis.

field_of_view may indicate the field of view degree of the region associated with the media sample of the referenced track.

“duration” may indicate the duration of the corresponding spherical coordinate sample. The time unit of this value may be a timescale provided by ‘mvhd’ or the ‘mdhd’ box of the metadata track.

“interpolate” may indicate time continuity for continuous samples. In an embodiment, if “interpolate” is true, the application may linearly interpolate the ROI coordinate values between the previous sample and the current sample. If “interpolate” is false, interpolation between the previous sample and the current sample may not be performed. The interpolation value of the sync samples for the ROI metadata track is 0.

According to an aspect of the present invention, a method of transmitting omnidirectional video is disclosed.

FIG. 49 is a flowchart illustrating a method of transmitting an omnidirectional video according to an embodiment of the present invention.

A method of transmitting an omnidirectional video according to an embodiment of the present invention may include acquiring an image for the omnidirectional video (SH49100), projecting the image for the omnidirectional video onto a three-dimensional projection structure (SH49200), packing the image projected onto the three-dimensional projection structure in a 2D frame (SH49300), encoding the image packed into the 2D frame (SH49400), and transmitting a data signal containing the encoded image and metadata about the omnidirectional video (SH49500).

In step SH49100 of acquiring an image for an omnidirectional video, an image for an omnidirectional video may be acquired. As described above with reference to FIGS. 1, 2, and 4, the image for the omnidirectional video may be obtained by capturing an image for the omnidirectional video using an omnidirectional camera (360-degree camera, VR camera) or by generating data corresponding to the omnidirectional video.

Step SH49100 of acquiring an image for an omnidirectional video may correspond to the capturing process t1010 of FIG. 1, the operation in the data input unit of FIG. 2, and the acquisition process of FIGS. 43, 46, and 47.

Step SH49200 of projecting the image for the omnidirectional video onto a three-dimensional projection structure may include projecting an image for the omnidirectional video to a 3D projection structure or a 3D model. In an embodiment, the 3D projection structure or the 3D model may be a sphere, a cube, a cylinder, or a pyramid.

Step SH49200 of projecting the image for the omnidirectional video onto the three-dimensional projection structure may correspond to the projection of the preparation process t1010 in FIG. 1, the operation in the projection processor of FIG. 2, the projection of FIG. 4, and the projection of the projection/mapping process of FIGS. 43, 46, and 47.

In an embodiment, the method of transmitting an omnidirectional video may further include a stitching step of connecting images for the omnidirectional video, which is between step SH49100 of acquiring an image for the omnidirectional video and step SH49200 of projecting the image for the omnidirectional video onto the three-dimensional projection structure. That is, the images for the omnidirectional video may be connected through stitching, and the connected images may be projected onto the 3D projection structure.

Step SH49300 of packing the image projected onto the three-dimensional projection structure in a 2D frame may be a step of mapping the three-dimensional image projected onto the three-dimensional projection structure onto a 2D frame. The three-dimensional image projected onto the three-dimensional projection structure may be presented through the three-dimensional region information, and the image packed into the 2D frame may be presented through the two-dimensional region information.

Here, the two-dimensional region information and the three-dimensional region information may correspond to each other. That is, an region or a point in the 2D frame indicated by the two-dimensional region information may correspond to an region or a point in the three-dimensional projection structure indicated by the three-dimensional region information.

The two-dimensional region information may be the information described with reference to FIGS. 12, 13, 37, 40, 44, and 45, and the three-dimensional region information may be the information described with reference to FIGS. 14, 15, 16, 17, 18, 38, 40, 41, 44 and 45. In addition, the two-dimensional region information and the three-dimensional region information may be information included in the metadata about the omnidirectional video.

Step SH49300 of packing the image projected onto the three-dimensional projection structure in a 2D frame may correspond to the 2D image mapping in the preparation process t1010 of FIG. 1, the 2D projection operation of the proejection processor of FIG. 2, the mapping process of the projection and mapping of FIG. 4, and the mapping of the projection/mapping process of FIGS. 43, 46, and 47.

In an embodiment, step SH49300 of packing an image projected onto the three-dimensional projection structure in a 2D frame may include dividing the image projected onto the three-dimensional projection structure into predetermined regions; packing sub-images divided by the predetermined regions in a 2D frame.

The step of dividing the image projected onto the three-dimensional projection structure into predetermined regions and the step of packing the sub-images divided by the predetermined regions in a 2D frame may correspond to the region-wise packing process of FIG. 1, the operation of the region-wise packing unit of FIG. 2, and the region-wise packing process of FIG. 4. If region-wise packing has been performed, the sub-images divided by the predetermined regions may correspond to the packed frames. If region-wise packing has not been performed, the 2D frame may be the same as the packed frame.

Step SH49400 of encoding the image packed into the 2D frame may be a step of encoding the packed image according to a predetermined encoding scheme.

Step SH49400 of encoding the image packed into the 2D frame may correspond to the encoding process of the preparation process t1010 of FIG. 1 and the operation of the data encoder of FIG. 2, and the video encoding process of FIGS. 43, 46, and 47.

In an embodiment, if region-wise packing has been performed, step SH49400 of encoding the image packed into the 2D frame may be a step of encoding a packed image corresponding to each region. Here, different encoding schemes may be used for packed images.

Step SH49500 of transmitting a data signal including the encoded image and the metadata about the omnidirectional video may be a step of transmitting the data signal including the encoded image and the metadata about the omnidirectional video to the reception device.

Step SH49500 of transmitting the data signal including the encoded image and the metadata about the omnidirectional video may correspond to the transmission process of FIG. 1 and the operation in the transmitter of FIG. 2 and the delivery shown in FIG. 4.

In an embodiment, the data signal may be a broadcast signal, and the encoded image and metadata about the omnidirectional video may be transmitted over the broadcast signal.

In an alternative embodiment, the encoded image may be transmitted over a broadcast network and the metadata about the omnidirectional video may be transmitted over a broadband network. Alternatively, the encoded image may be transmitted over a broadband network and the metadata about the omnidirectional video may be transmitted over a broadcast network. Alternatively, both the encoded image and the metadata about the omnidirectional video may be transmitted over a broadband network.

The metadata about the omnidirectional video may refer to information necessary for the reception device to process the omnidirectional video. The metadata about the omnidirectional video may correspond to all or part of the metadata shown in FIG. 8 and may refer to the information shown in FIGS. 12 to 19, 20 to 23, 25, 27, 28, 30 to 38, 40, 41, 44, 45 and/or 48.

In a specific embodiment, the metadata about the omnidirectional video may include 3D region information about the image projected onto the 3D projection structure or 2D region information about the image packed into the 2D frame. Here, the 2D region information may be the information described with reference to FIGS. 12, 13, 37, 40, 44 and 45 and the 3D region information may be the information described with reference to FIGS. 14, 15, 16, 17, 18, 38, 40, 41, 44 and 45. Further, the 2D region information and the 3D region information may be information included in the metadata about the omnidirectional video.

In a more specific embodiment, the 3D region information may be used to indicate a region of a 3D image projected onto a 3D spherical projection structure. That is, the 3D region information may be information indicating a region of a spherical surface (see FIGS. 14, 15, 16, 17, 18, 38, 40, 41, 44 and 45). In this embodiment, the 3D region information may include horizontal-field-of-view information indicating a horizontal field of view and vertical-field-of-view information indicating a vertical field of view. In addition, the 3D region information may further include yaw information and pitch information which indicate a yaw axis angle and a pitch axis angle for indicating the centers of the horizontal field of view and the vertical field of view. In an embodiment, the horizontal-field-of-view information and the vertical-field-of-view information may be field_of_view, min_field_of_view, max_field_of_view, horizontal_field_of view, vertical_(—) field_of_view, reference_width, reference_height, width, height, reference_horizontal_field_of_view, reference_vertical_field_of_view, reference_viewpoint_yaw_range, reference_viewpoint_pitch_range, horizontal_field_of_view, vertical_field_of_view, viewpoint_yaw_range and/or viewpoint_pitch_range of FIGS. 14 to 18.

In an embodiment, the yaw information and the pitch information which indicate a yaw axis angle and a pitch axis angle for indicating the centers of the horizontal field of view and the vertical field of view may be center_yaw, yaw, center_pitch, pitch, reference_yaw_center, reference_pitch_c enter, reference_roll_center, yaw_center, pitch_center and/or roll_center of FIGS. 14 to 18.

In a more specific embodiment, the metadata about the omnidirectional video may include region type information for identifying a region type specifying a region of the surface of a sphere. The region type may include a first type that specifies an region through four great circles belonging to the sphere and a second type that specifies an region through two great circles and two small circles belonging to the sphere The great circles may represent circles passing through the center of the sphere, and the small circles may represent circles not passing through the center of the sphere. Here, the region type may refer to region_type described in FIGS. 16 to 19.

The metadata about the omnidirectional video may indicate ROI information, recommended region information, or information about the viewpoint of the omnidirectional video intended by the producer.

The metadata about the omnidirectional video may be transmitted through a ISOBMFF file format, a DASH MPD/segment, a PES packet or an adaptation field of MPEG-2 TS, and/or an SEI message of VCL.

In an embodiment, the metadata about the omnidirectional video may be included in an adaptation set of DASH (Dynamic Adaptive Streaming over HTTP) and transmitted. This has been described above in detail with reference to FIGS. 22 to 29.

In another embodiment, the metadata about the omnidirectional video may be included in a PES (Packetized Elementary Stream) packet or an adaptation field of an MPEG-2 TS TS and transmitted. This has been described above in detail with reference to FIGS. 30 to 39.

In another embodiment, the metadata about the omnidirectional video may be included in an SEI (Supplemental Enhancement Layer) message of the VCL (Video Coding layer). This has been described above in detail with reference to FIGS. 40 to 42. The description thereof will be described in detail in FIGS. 40 to 42 and the description of the drawings. In an embodiment, a region of the sphere may be specified through four great circles belonging to the sphere as described above with reference to FIG. 41.

According to another aspect of the present invention, a device for transmitting omnidirectional video is disclosed.

FIG. 50 is a block diagram of a device for transmitting omnidirectional video according to an embodiment of the present invention.

The device for transmitting omnidirectional video according to an embodiment of the present invention may include an image acquisition unit H50100 for acquiring an image for the omnidirectional video, a projection unit H50200 for projecting the image for the omnidirectional video onto a 3D projection structure, a packing unit H50300 for packing the image projected onto the 3D projection structure into a 2D frame, an encoder H50400 for encoding the image packed into the 2D frame, and a transmission unit H50500 for transmitting a data signal including the encoded image and metadata about the omnidirectional video.

The operation of the image acquisition unit H50100 may correspond to step H49100 of acquiring an image for omnidirectional video in the method of transmitting omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 49 and thus description of step H49100 is applicable thereto.

The operation of the projection unit H50200 may correspond to step H49200 of projecting the image for the omnidirectional video onto a 3D projection structure in the method of transmitting omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 49 and thus description of step H49200 is applicable thereto.

The operation of the packing unit H50300 may correspond to step H49300 of packing the image projected onto the 3D projection structure into a 2D frame in the method of transmitting omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 49 and thus description of step H49300 is applicable thereto.

The operation of the encoder H50400 may correspond to step H49400 of encoding the image packed into the 2D frame in the method of transmitting omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 49 and thus description of step H49400 is applicable thereto.

The operation of the transmission unit H50500 may correspond to step H49500 of transmitting a data signal including the encoded image and metadata about the omnidirectional video in the method of transmitting omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 49 and thus description of step H49500 is applicable thereto.

In an embodiment, the device for transmitting omnidirectional video may further include a stitcher (not shown). The stitcher may connect images for the omnidirectional video. The operation of the stitcher may correspond to the stitching step in the method of transmitting omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 49 and thus description of the stitching step is applicable thereto.

In an embodiment, the packing unit H50300 may divide the image projected onto the 3D projection structure into predetermined regions and pack sub-images divided by the predetermined regions into a 2D frame. Such region-wise packing operation of the packing unit may correspond to the region-wise packing step in the method of transmitting omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 49 and thus description of the region-wise packing step is applicable thereto.

The metadata about the omnidirectional video may refer to information necessary for a reception device to process the omnidirectional video. The metadata about the omnidirectional video has been described above in the method of transmitting omnidirectional video according to an embodiment of the present invention.

According to another aspect of the present invention, a method of receiving omnidirectional video is provided.

FIG. 51 is a flowchart illustrating a method of receiving omnidirectional video according to an embodiment of the present invention.

The method of receiving omnidirectional video according to an embodiment of the present invention may include step SH51100 of receiving a data signal including an image for the omnidirectional video and metadata about the omnidirectional video, step SH51200 of parsing the metadata about the omnidirectional video, step SH51300 of decoding the image for the omnidirectional video and step SH51400 of re-projecting the image for the omnidirectional video onto a 3D mode.

The method of receiving omnidirectional video according to an embodiment of the present invention may be a method for a reception side which corresponds to the above-described method of transmitting omnidirectional video according to an embodiment of the present invention.

Step SH51100 of receiving a data signal including an image for the omnidirectional video and metadata about the omnidirectional video may be a step of receiving a data signal including an image for the omnidirectional video and metadata about the omnidirectional video, and the data signal may be transmitted from a transmission device.

The image for the omnidirectional video may be the image encoded in the method of transmitting omnidirectional video according to an embodiment of the present invention. That is, the image for the omnidirectional video may be the encoded image generated through steps H49100, H49200, H49300 and H49400 of FIG. 49.

Step SH51100 of receiving a data signal including an image for the omnidirectional video and metadata about the omnidirectional video may correspond to the reception process of FIG. 1, the operation of the reception unit shown in FIG. 3 and the reception process of FIG. 4.

In an embodiment, the data signal may be a broadcast signal, and the image for the omnidirectional video and the metadata about the omnidirectional video may be transmitted through the broadcast signal.

In an alternative embodiment, the image for the omnidirectional video may be transmitted over a broadcast network and the metadata about the omnidirectional video may be transmitted over a broadband network. Alternatively, the image for the omnidirectional video may be transmitted over a broadband network and the metadata about the omnidirectional video may be transmitted over a broadcast network. Alternatively, both the image for the omnidirectional video and the metadata about the omnidirectional video may be transmitted over a broadband network.

The metadata about the omnidirectional video may refer to information necessary for the reception device to process the omnidirectional video. The metadata about the omnidirectional video may correspond to all or part of the metadata shown in FIG. 8 and may refer to the information of FIGS. 12 to 19, 20 to 23, 25, 27 and 28, 30 to 38, 40 and 41, 44 and 45 and/or 48.

In a specific embodiment, the metadata about the omnidirectional video may include 3D region information about the image projected onto the 3D projection structure or 2D region information about the image packed into the 2D frame. Here, the 2D region information may be the information described with reference to FIGS. 12, 13, 37, 40, 44 and 45 and the 3D region information may be the information described with reference to FIGS. 14, 15, 16, 18, 38, 40, 41, 44 and 45. Further, the 2D region information and the 3D region information may be information included in the metadata about the omnidirectional video.

In a more specific embodiment, the 3D region information may be used to indicate a region of a 3D image projected onto a 3D spherical projection structure. That is, the 3D region information may be information indicating a region of a sphere (see FIGS. 14, 15, 16, 17, 18, 38, 40, 41, 44, and 45). In this embodiment, the 3D region information may include horizontal-field-of-view information indicating a horizontal field of view and vertical-field-of-view information indicating a vertical field of view. In addition, the 3D region information may further include yaw information and pitch information which indicate a yaw axis angle and a pitch axis angle for indicating the centers of the horizontal field of view and the vertical field of view. In an embodiment, the horizontal-field-of-view information and the vertical-field-of-view information may be field_of_view, min_field_of_view, max_field_of_view, horizontal_field_of_view, vertical_field_of_view, reference_width, reference_height, width, height, reference_horizontal_field_of_view, reference_vertical_field_of_view, reference_viewpoint_yaw_range, reference_viewpoint_pitch_range, horizontal_field_of_view, vertical_field_of_view, viewpoint_yaw_range and/or viewpoint_pitch_range of FIGS. 14 to 18.

In an embodiment, the yaw information and the pitch information which indicate a yaw axis angle and a pitch axis angle for indicating the centers of the horizontal field of view and the vertical field of view may be center_yaw, yaw, center_pitch, pitch, reference_yaw_center, reference_pitch_center, reference_roll_center, yaw_center, pitch_center and/or roll_center shown in FIGS. 14 to 18.

In a more specific embodiment, the metadata about the omnidirectional video may include region type information for identifying a region type specifying a region of the surface of a sphere. The region type may include a first type that specifies an region through four great circles belonging to the sphere and a second type that specifies an region through two great circles and two small circles belonging to the sphere The great circles may represent circles passing through the center of the sphere, and the small circles may represent circles not passing through the center of the sphere. Here, the region type may refer to region_type described in FIGS. 16 to 19.

The metadata about the omnidirectional video may indicate ROI information, recommended region information, or information about the viewpoint of the omnidirectional video intended by the producer.

The metadata about the omnidirectional video may be transmitted through a ISOBMFF file format, a DASH MPD/segment, a PES packet or an adaptation field of MPEG-2 TS, and/or an SEI message of VCL.

In an embodiment, the metadata about the omnidirectional video may be included in an adaptation set of DASH (Dynamic Adaptive Streaming over HTTP) and transmitted. This has been described above in detail with reference to FIGS. 22 to 29.

In another embodiment, the metadata about the omnidirectional video may be included in a PES (Packetized Elementary Stream) packet or an adaptation field of an MPEG-2 TS TS and transmitted. This has been described above in detail with reference to FIGS. 30 to 39.

In another embodiment, the metadata about the omnidirectional video may be included in an SEI (Supplemental Enhancement Layer) message of the VCL (Video Coding layer). This has been described above in detail with reference to FIGS. 40 to 42. The description thereof will be described in detail in FIGS. 40 to 42 and the description of the drawings. In an embodiment, a region of the sphere may be specified through four great circles belonging to the sphere as described above with reference to FIG. 41.

Step SH51200 of parsing the metadata about the omnidirectional video may be a step of parsing the metadata about the omnidirectional video included in the data signal.

As described above, the metadata about the omnidirectional video may be transmitted through ISOBMFF, a DASH MPD/segment, a PES packet or an adaptation field of an MPEG-2 TS and/or an SEI message of VCL and thus may be parsed at each level.

Step SH51300 of decoding the image for the omnidirectional video may be a step of decoding an encoded image using a decoding scheme corresponding to the encoding scheme used for the encoded image.

Step SH51300 of decoding the image for the omnidirectional video may correspond to the decoding process of FIG. 1, the operation of the data decoder of FIG. 3, the video decoding or image decoding process of FIG. 4, and the video decoding process of FIGS. 43, 46, and 47.

In an embodiment, if region-wise packing has been performed, step SH51300 of decoding the image for the omnidirectional video may be a step of decoding a packed image corresponding to each region. Here, different decoding schemes may be used for packed images.

In an embodiment in which the metadata about the omnidirectional video is transmitted through an SEI message of VCL, the metadata about the omnidirectional video may be extracted in step SH51300.

Step SH51400 of re-projecting the image for the omnidirectional video onto a 3D model may be a step of re-projecting the image packed into a 2D frame onto a 3D model. Since the image for the omnidirectional video decoded through step SH51300 refers to an image packed into a 2D frame, step SH51400 may refer to a step of re-projecting the image packed into the 2D frame onto a 3D model. Here, the 3D model may be the same as the 3D projection structure in the method of transmitting omnidirectional video according to an embodiment of the present invention.

Step SH51400 of re-projecting the image for the omnidirectional video on the 3D model may correspond to the rendering process t1030 of FIG. 1, the operation of the re-projection processor of FIG. 3, the video rendering process of FIG. 4, and the re-projection process and the VR video rendering process of FIGS. 43, 46, and 47.

In an embodiment, the method of receiving omnidirectional video according to an embodiment of the present invention may further include a feedback step. The feedback step is a step of outputting viewport information or rotation information of a user device. Data corresponding to a view region may be processed on the basis of the viewport information or rotation information of the user device. Feedback information including the viewport information or rotation information of the user device may be provided prior to the re-projection step, rendering step, image decoding step or a transmission file or segment decapsulation step. Further, the feedback information may be transmitted to a transmission side.

The feedback step may correspond to the feedback process of FIG. 1, the operation of the feedback processor of FIG. 3, the tracking process of a VR application in FIG. 4, and the tracking process (head/eye tracking) in FIGS. 46 and 47.

According to another aspect of the present invention, a device for receiving omnidirectional video is provided.

FIG. 52 is a block diagram of a device for receiving omnidirectional video according to an embodiment of the present invention.

The device for receiving omnidirectional video according to an embodiment of the present invention may include a reception unit H52100 for receiving a data signal including an image for the omnidirectional video and metadata about the omnidirectional video, a metadata parser H52200 for parsing the metadata about the omnidirectional video, a decoder H52300 for decoding the image for the omnidirectional video, and a rendering unit H52400 for re-projecting the image for the omnidirectional video onto a 3D model.

The operation of the reception unit H52100 may correspond to step SH51100 of receiving a data signal including an image for the omnidirectional video and metadata about the omnidirectional video in the method of receiving omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 51 and thus description of step SH51100 is applicable thereto.

The operation of the metadata parser H52200 may correspond to step SH51200 of parsing the metadata about the omnidirectional video in the method of receiving omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 51 and thus description of step SH51200 is applicable thereto.

The operation of the decoder H52300 may correspond to step SH51300 of decoding the image for the omnidirectional video in the method of receiving omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 51 and thus description of step SH51300 is applicable thereto.

The operation of the rendering unit H52400 may correspond to step SH51400 of re-projecting the image for the omnidirectional video onto a 3D model in the method of receiving omnidirectional video according to an embodiment of the present invention described above with reference to FIG. 51 and thus description of step SH51400 is applicable thereto.

In an embodiment, the device for receiving omnidirectional video may further include a feedback processor (not shown). The feedback processor may generate and output viewport information and/or rotation information by tracking viewport and/or rotation of a user device.

The metadata about the omnidirectional video may refer to information necessary for a reception device to process the omnidirectional video. The metadata about the omnidirectional video has been described above in the method of receiving omnidirectional video according to an embodiment of the present invention.

The internal components of the above-described devices may be processors which execute consecutive procedures stored in memories or hardware components. The processors or hardware components may be provided to the inside/outside of the devices.

The aforementioned modules may be omitted or replaced by other modules which perform similar/identical operations according to embodiments.

Each of the aforementioned parts, modules or units may be a processor or a hardware part designed to execute a series of execution steps stored in a memory (or a storage unit). Each step described in the above-mentioned embodiments may be implemented by processors or hardware parts. Each module, each block, and/or each unit described in the above-mentioned embodiments may be realized by a processor/hardware. In addition, the above-mentioned methods of the present invention may be realized by code written in recoding media configured to be read by a processor so that the code may be read by the processor provided by the apparatus.

Although the description of the present invention is explained with reference to each of the accompanying drawings for clarity, it is possible to design new embodiments by merging the embodiments shown in the accompanying drawings with each other. If a recording medium readable by a computer, in which programs for executing the embodiments mentioned in the foregoing description are recorded, is designed by those skilled in the art, it may fall within the scope of the appended claims and their equivalents.

The devices and methods according to the present invention may be non-limited by the configurations and methods of the embodiments mentioned in the foregoing description. The embodiments mentioned in the foregoing description may be configured in a manner of being selectively combined with one another entirely or in part to enable various modifications.

In addition, a method according to the present invention may be implemented with processor-readable code in a processor-readable recording medium provided to a network device. The processor-readable medium may include all kinds of recording devices capable of storing data readable by a processor. The processor-readable medium may include one of ROM, RAM, CD-ROM, magnetic tapes, floppy disks, optical data storage devices, and the like and also include carrier-wave type implementation such as a transmission via Internet. Furthermore, as the processor-readable recording medium is distributed to a computer system connected via a network, processor-readable code may be saved and executed in a distributed manner.

Although the invention has been described with reference to the exemplary embodiments, those skilled in the art will appreciate that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention described in the appended claims. For example, those skilled in the art may use each construction described in the above embodiments in combination with each other. Accordingly, the invention should not be limited to the specific embodiments described herein, but should be accorded the broadest scope consistent with the principles and novel features disclosed herein.

It will be appreciated by those skilled in the art that various modifications and variations may be made in the present invention without departing from the spirit or scope of the inventions. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.

Both apparatus and method inventions are mentioned in this specification and descriptions of both of the apparatus and method inventions may be complementarily applicable to each other.

MODE FOR INVENTION

Various embodiments have been described in the best mode for carrying out the invention.

INDUSTRIAL APPLICABILITY

The present invention is available in a series of broadcast signal provision fields.

It will be apparent to those skilled in the art that various modifications and variations may be made in the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents. 

What is claimed is:
 1. A method of transmitting omnidirectional video comprising: acquiring an image for the omnidirectional video; projecting the image for the omnidirectional video onto a 3D projection structure; packing the image projected onto the 3D projection structure in a 2D frame; encoding the image packed into the 2D frame; and transmitting a data signal containing the encoded image and metadata about the omnidirectional video, wherein the metadata about the omnidirectional video comprises 3D region information about the image projected onto the 3D projection structure, wherein the 3D projection structure corresponds to a sphere, wherein the 3D region information is information used to indicate a region of a surface of a sphere, and comprises yaw information and pitch information indicating a yaw axis angle and a pitch axis angle of a center of the region, and range information indicating a range of the region.
 2. The method according to claim 1, wherein the metadata about the omnidirectional video further comprises region type information for identifying a region type specifying the region of the surface of the sphere.
 3. The method according to claim 2, wherein the region type comprises a first type for specifying a region through four great circles belonging to the sphere and a second type for specifying a region through two great circles and two small circles belonging to the sphere.
 4. The method according to claim 3, wherein the great circles represent circles passing through the center of the sphere, and the small circles represent circles not passing through the center of the sphere.
 5. The method according to claim 1, wherein the metadata about the omnidirectional video is included in an SEI message (Supplemental Enhancement Layer) of a video coding layer (VCL).
 6. The method according to claim 5, wherein the region of the surface of the sphere is specified through four great circles belonging to the sphere.
 7. The method according to claim 1, wherein the metadata about the omnidirectional video is transmitted in a Packetized Elementary Stream (PES) packet of an MPEG-2 TS or an adaptation field of a transport stream (TS).
 8. The method according to claim 1, wherein the metadata about the omnidirectional video is transmitted in an adaptation set of dynamic adaptive streaming over HTTP (DASH).
 9. The method according to claim 1, wherein the packing of the image comprises: dividing the image projected onto the 3D projection structure into predetermined regions; and packing sub-images divided into the predetermined regions into a 2D frame.
 10. An device for transmitting omnidirectional video, comprising: an image acquisition unit configured to acquire an image for the omnidirectional video; a projection unit configured to project the image for the omnidirectional video onto a 3D projection structure; a packing unit configured to pack the image projected onto the 3D projection structure in a 2D frame; an encoder configured to encode the image packed into the 2D frame; and a transmission unit configured to transmit a data signal containing the encoded image and metadata about the omnidirectional video, wherein the metadata about the omnidirectional video comprises 3D region information about the image projected onto the 3D projection structure, wherein the 3D projection structure corresponds to a sphere, wherein the 3D region information is information used to indicate a region of a surface of a sphere, and comprises yaw information and pitch information indicating a yaw axis angle and a pitch axis angle of a center of the region, and range information indicating a range of the region.
 11. A method of receiving omnidirectional video comprising: receiving a data signal containing an image for omnidirectional video and metadata about the omnidirectional video; parsing the metadata about the omnidirectional video; decoding the image for the omnidirectional video; and re-projecting the image for the omnidirectional video onto a 3D model, wherein the metadata about the omnidirectional video comprises 3D region information about the image projected onto the 3D projection structure, wherein the 3D projection structure corresponds to a sphere, wherein the 3D region information is information used to indicate a region of a surface of a sphere, and comprises yaw information and pitch information indicating a yaw axis angle and a pitch axis angle of a center of the region, and range information indicating a range of the region.
 12. An device for receiving omnidirectional video, comprising: a receiver configured to receive a data signal containing an image for omnidirectional video and metadata about the omnidirectional video; a metadata parser configured to parse the metadata about the omnidirectional video; a decoder configured to decode the image for the omnidirectional video; and a rendering unit configured to re-project the image for the omnidirectional video onto a 3D model, wherein the metadata about the omnidirectional video comprises 3D region information about the image projected onto the 3D projection structure, wherein the 3D projection structure corresponds to a sphere, wherein the 3D region information is information used to indicate a region of a surface of a sphere, and comprises yaw information and pitch information indicating a yaw axis angle and a pitch axis angle of a center of the region, and range information indicating a range of the region. 